Give your agent the right tools
Discover approved operations, use exact inputs, and keep access scoped to your workspace.
Tools make reviewed operations available to an agent. The visible catalog is filtered by workspace, account role, OAuth client grant, tool policy, and binding readiness.
Approve a tool
An owner reviews the intended connector operation and enables its exact binding for the appropriate role or client. A ready tool is tied to a reviewed connector and contract version.
Owners can inspect policies and test exact inputs without an AI model from the platform. Grant access only to the reads needed for the intended workflow.
Discover before executing
- Call
convergesense_get_contextto confirm the workspace and permissions. - Search with
convergesense_search_tools. - Read the chosen tool's contract with
convergesense_describe_tool. - Supply the exact accepted inputs to
convergesense_run_tool. - If pending, poll the returned job with
convergesense_get_job.
Use exact device, ticket, service, or interface identifiers when a contract requires them. Resolve an ambiguous identity before reading additional customer or equipment context.
Keep one request identity
Each execution has an idempotency key. Reusing that key for the same logical request returns the original job instead of issuing another command.
After a timeout or ambiguous result, retrieve the original job. Do not silently switch to a new key and repeat the operation.
Read freshness correctly
Completed results include the Engine's actual observation time, freshness, snapshot status, warning codes, and connector and contract digests.
| Freshness | What to communicate |
|---|---|
fresh | Report the supplied observation time and result. |
cached | Explain that the result came from a retained observation. |
stale | Keep the age and warnings visible; avoid presenting it as current. |
The policy selection follows the configured cache behavior. live requests bypass the applicable warm cache when supported. A fresh observation does not prove that an earlier intermittent fault never occurred.
Understand missing tools
A tool can be absent because its binding is unready, a contract changed, the grant lacks access, or a workspace policy disables it. Unknown or unauthorized tools are excluded from discovery.
Use Troubleshooting to narrow down the cause and the MCP reference for request shapes.