Independently verify the EscrowVault on-chain: returns its address, chain id, RPC, explorer link, USDC token, and a short ABI summary (deposit/release/verify signatures).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| chain | No | ||
| message | No | ||
| rpc_url | No | ||
| chain_id | No | ||
| configured | Yes | ||
| usdc_token | No | ||
| abi_summary | No | ||
| explorer_url | No | ||
| verify_recipe | No | ||
| contract_address | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description carries a lighter burden. It adds value by scoping the read to the EscrowVault and specifying the exact returned fields, including the ABI summary, which the structured annotations do not convey.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The entire description is one compact sentence with a front-loaded action ('Independently verify...') followed by a tight list of returns. There is no filler, redundancy, or unnecessary detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With zero parameters, strong non-destructive annotations, and an output schema present, the description supplies enough return-value context for an agent to invoke the tool successfully. The term 'verify' could be slightly more explicit about what counts as a successful verification, but the listed outputs largely cover operational expectations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters; the input schema explicitly says there are no arguments and that the owner is derived from the authenticated principal. With no parameters to document, the description does not need to add parameter-level meaning, and the schema coverage is complete.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific operation—independently verify the EscrowVault on-chain—and enumerates the returned data (address, chain id, RPC, explorer link, USDC token, ABI summary). This is clear and concrete, but it does not explicitly contrast with related siblings like get_agent_contract or data_session_attach_escrow, so there is no sibling differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No sentence explains when to choose this tool over the sibling contract/escrow tools, nor does it list exclusions or prerequisites. The phrase 'independently verify' implies a verification context, but that is inferred rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tools occupy adjacent territory: data_session_fund, data_session_funding_package, and data_session_attach_escrow all relate to funding, while a2awire_guide and get_recommended_action both provide navigation guidance. Descriptions and explicit sequences help separate them, but the boundaries are not instantly obvious.
Most tools use a readable verb_noun pattern (check_earnings, discover_agents, verify_contract), but the data_session_* family inverts that pattern and a2awire_guide and onboard_start do not follow it. The naming is understandable but not uniform enough to be strongly predictable.
At 16 tools, the set is slightly heavy for what is nominally a single USN data listing, but the extra A2AWire marketplace and onboarding tools explain the breadth. It feels bloated rather than unwieldy.
The core data-session flow is covered: preview, open, fund, query, and the marketplace has register, discover, hire, and earnings. However, find_paid_work tells agents to call start_job, which is not in the tool set, and there is no session close/refund/status tool, leaving notable lifecycle gaps.