Skip to main content
A Tool is a synthetic service with declared operations, state, and behavior. It can represent a dependency such as a mailbox, calendar, CRM, or a private service you author. Tools are optional. An agent that answers from supplied context can be simulated without one. An agent that changes external systems can route those actions through the synthetic dependencies it needs.

​
Definitions, data, and instances

  • A build pins a Tool’s executable behavior and operation schemas.
  • A dataset pins starting records for that build.
  • An instance is a running copy with its own state, seed, allowed operations, and expiry.
Two instances of the same Tool can use different datasets and evolve independently. Several Tools can participate in one simulation.

​
Connect using a declared interface

Use the issued semantic HTTP or MCP connection. Some Tools also declare HTTP routes or a browser application. Inspect the selected release’s interfaces and fidelity; a familiar product name does not guarantee its complete native API. API calls, MCP operations, and browser actions use the same synthetic instance state. They never require your real service account. Start with Tool setup, connections, or authoring a Tool.