Tools

MAARS does not give every agent every power. Tools are intentionally defined and scoped so each phase can do what it needs without quietly taking on responsibilities that belong elsewhere.

01Tooling philosophy

02Tool families

The tool surface is small on purpose: read state, search outside knowledge, or execute code in the sandbox.

03Capability profile

Agents are told about the execution environment even when they cannot call every tool directly.

04Allocation by stage and phase

The same tool can be available in one phase and intentionally absent in another.

05Sandbox semantics

The Docker tools are more than “run code”; they define how task execution persists across the stage.

06Extension rules

Adding a tool is easy mechanically, but the important part is preserving the stage boundary it belongs to.