Skip to main content
A Tool’s contract declares what can be called and what those calls can change. Use only declared interfaces. A service name or logo is not a promise that every provider-native endpoint is supported.

​
One instance, coherent data

API, MCP, and supported browser actions must use the same instance state. Your selected dataset provides its starting records. Independent instances and independent cases do not share mutable data.

​
Review a custom model

Authoring publishes only explicitly selected source and contracts. Inspect build diagnostics and supplied conformance results before using the Tool in a simulation. Conformance proves the supplied cases were exercised, not that the whole external service was replicated. A quality score about an agent’s output is also not a certification of Tool fidelity.