Skip to main content
Glama

x402 Data API (Crypto, DeFi, SEC EDGAR, Search, Embeddings, Whisper, OCR)

agent_escrow_arbitration

[$0.15] Resolve agent-to-agent escrow disputes by cross-referencing task spec hashes, delivery hashes, and state attestations into a persisted SLA verdict.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "agent_escrow_arbitration"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeout_msNoOptional deadline in ms. If the local LLM would exceed it, the response comes back fast with "degraded": true and non-LLM/cached data
attestation_idNoOptional state_attestations ID anchoring the deliverable
task_spec_hashNoSHA-256 or keccak256 hash of the agreed task specification
delivery_payload_hashNoSHA-256 or keccak256 hash of the submitted agent deliverable

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full behavioral burden. It does disclose two valuable traits: the operation persists a verdict (a side effect) and it costs $0.15. It does not state what happens when hashes are omitted (all four parameters are optional), what permissions or prerequisites are needed, or whether a persisted verdict is idempotent or overwritable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with the price front-loaded and the action-leading verb, with no filler. The middle clause is dense with compound nouns, but every part carries meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a dispute-resolution tool with zero required parameters, no annotations, and no output schema, the description should explain the verdict's shape and behavior under partial input. It covers the inputs and the persistence outcome but leaves the result contract and missing-parameter behavior unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3 regardless. The description clarifies that the two hashes plus the attestation are cross-referenced together into a verdict, which gives a hint of how they combine, but adds no format, precedence, or fallback semantics beyond what the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ("Resolve") plus a specific resource ("agent-to-agent escrow disputes") and even the method (cross-referencing spec hashes, delivery hashes, attestations). It does not name or distinguish itself from related siblings such as crypto_state_attestation or agent_reputation_mesh, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The domain implies when to call it, but there is no explicit trigger condition, no prerequisite guidance (e.g., that an attestation_id anchors the deliverable), and no statement of when not to use it or what alternative handles related cases. The agent must infer invocation criteria from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources