Confirm delivery and release escrowed USDC to the seller. Only call this when you've verified the service/product was delivered correctly.
| Name | Required | Description | Default |
|---|---|---|---|
| escrow_id | Yes | The escrow ID to release |
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 description discloses the core behavior — releasing escrowed USDC to the seller — which is essential. With no annotations, it carries the full transparency burden, but it does not mention that the release is irreversible or that it finalizes/closes the escrow. This is a notable gap for a financial mutation action.
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 exactly two sentences. The first sentence delivers the purpose, and the second provides a usage condition. There is no wasted or redundant content, and it is well 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 simple tool with one parameter and no output schema, the description adequately covers the core purpose and usage guidance. It could be improved by noting that the release is final or that it closes the escrow, but the current description is sufficient for an agent to select and invoke the tool correctly.
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 input schema provides 100% coverage with a clear description for escrow_id ('The escrow ID to release'). The tool description adds no additional parameter semantics beyond the schema, so the baseline of 3 is appropriate.
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 clearly uses specific verbs 'confirm delivery' and 'release' with a direct resource ('escrowed USDC to the seller'). It distinguishes this tool from siblings like escrow_create, escrow_dispute, and escrow_status by indicating it is the final settlement step after delivery confirmation.
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?
The instruction 'Only call this when you've verified the service/product was delivered correctly' provides an explicit when-to-use and an implicit when-not-to-use condition. However, it does not explicitly name an alternative tool (e.g., escrow_dispute) for cases where delivery was not correct, which would strengthen the guidance.
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.
Most tools have distinct purposes, but there is some overlap between trust_gate, trust_onchain_quick, and trust_score_query, which all relate to checking agent trustworthiness. While each has a slightly different focus (quick check vs. full breakdown vs. decision recommendation), an agent might struggle to choose the right one in some scenarios. The escrow and payment tools are clearly differentiated.
The naming is mostly consistent with a verb_noun pattern (e.g., escrow_create, escrow_release, rate_service), but there are deviations like safe_pay (adjective_verb) and x402_protected_call (alphanumeric prefix). These outliers break the pattern slightly, though the majority of tools follow a clear convention.
With 10 tools, the count is well-scoped for the server's purpose of handling escrow, payments, and trust management. Each tool appears to serve a specific function in the workflow, from creating escrows to checking trust scores, without feeling excessive or insufficient for the domain.
The tool set provides comprehensive coverage for the escrow and payment domain, including creation, dispute, release, status checks, rating, and trust assessment. It supports both automated (safe_pay) and manual (x402_protected_call) workflows, with no obvious gaps in the lifecycle or functionality needed for secure transactions.