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?
The annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds that verification is on-chain and enumerates the returned data, but it adds no additional behavioral caveats such as network dependency or failure modes; this is acceptable but not rich.
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 description is a single dense sentence with a lead verb and a colon-separated output list. There is no filler, and the most important information is front-loaded.
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?
For a read-only, idempotent, zero-parameter tool with an output schema, the description covers purpose and expected return content in enough detail to support correct selection and invocation. No critical context appears missing.
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, and the input schema already states that ownership is derived from the authenticated principal. Baseline for zero-parameter tools is 4, and the description does not need to add parameter-level detail.
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 clear verb and resource ('Independently verify ... EscrowVault on-chain') and lists the exact returned fields, so an agent knows what the tool does. It does not explicitly contrast with sibling tools such as get_agent_contract or data_session_attach_escrow, so it stops short of full 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 guidance is given about when to call this tool instead of its siblings or when not to use it. The 'independently verify' phrasing implies a verification use case, but the description never names an alternative or states a precondition.
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.
Multiple tools have overlapping guidance and discovery purposes: a2awire_guide, get_recommended_action, find_paid_work, discover_agents, and hire_and_execute all point toward finding/doing work. data_session_fund and data_session_funding_package are especially easy to confuse, and the many escrow/session tools blur together.
Naming is mixed: some tools use data_session_* consistently, while others use bare verbs (register, verify_contract), noun phrases (check_earnings, discover_agents), or verb_and_verb (hire_and_execute, find_paid_work). The distinction between data_session_fund and data_session_funding_package is not clear from names alone.
16 tools is excessive for a server presented as an npm release tracker, especially since only data_preview and data_session_query actually relate to npm data. Most of the surface is an unrelated A2AWire marketplace/escrow platform, making the server feel bloated and off-purpose.
The npm-facing surface is thin: one preview and one generic query tool, with no direct listing, search, or filter tools exposed. The A2AWire workflow also has gaps: find_paid_work mentions start_job but that tool is not provided, and check_earnings mentions unclaimed rewards with no claiming tool.