Skip to main content
Glama

Quote an evidence pack

evidence_pack_quote
Read-onlyIdempotent

Price and how to buy a dated evidence pack over x402 (USDC on Base, 1 to 30 cents). About one period: edition (the depth file behind a final State of Agent Money edition: every agent and every payee of the period, the edition's figures and the period's book; id = YYYY-MM, YYYY-Qn or latest; 30 cents). About one agent: precheck (the routine check before you pay or hire it: level, last payment, live incidents, statement freshness, and with payto what that address is), liveness, paygraph (where it pays), drain, incidents, peer, builders (which apps build its transactions, ERC-8021), exit (did its wallet empty out: every window in which a new payee took most of its outflow in 72 hours, with where the money went next; candidates, never verdicts), trace (where did the money go: its exits followed live up to three hops, with each hop's issuer freeze, swap out of a freezable token and Tron activity), bundle, reval (a live re-probe) or statement (its last 24 statements with proofs). About one address: counterparty (which ranked agents paid it) or venue (what the address is: label, contract or key, who pays it, poisoning look-alike or not, live 48-hour flow). This tool does not pay; an x402-capable client fetches the returned URL, receives HTTP 402 with the exact price, and retries with a signed payment.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "<kind>"
    },
    "name": "evidence_pack_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoAgent token id, slug or wallet; for counterparty and venue, the 0x address (required; agent is accepted as the same field)
kindYesWhich pack to quote. Asking for a quote buys nothing
agentNoSame as id
paytoNoprecheck only, optional: the 0x address you are about to pay

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / kind / description
      Added value: +"Which pack to quote. Asking for a quote buys nothing"
  2. Changed3 schema fields changed
    • addedInput schema / properties / agent
      Added value: +{
      +  "description": "Same as id",
      +  "type": "string"
      +}
    • changedInput schema / properties / id / description
      Previous value: -"Agent token id, slug or wallet; for counterparty and venue, the 0x address"New value: +"Agent token id, slug or wallet; for counterparty and venue, the 0x address (required; agent is accepted as the same field)"
    • changedInput schema / required
      Previous value: -[
      -  "kind",
      -  "id"
      -]New value: +[
      +  "kind"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "precheck",
      -  "liveness",
      -  "paygraph",
      -  "drain",
      -  "exit",
      -  "trace",
      -  "incidents",
      -  "peer",
      -  "builders",
      -  "bundle",
      -  "reval",
      -  "statement",
      -  "counterparty",
      -  "venue"
      -]New value: +[
      +  "precheck",
      +  "liveness",
      +  "paygraph",
      +  "drain",
      +  "exit",
      +  "trace",
      +  "incidents",
      +  "peer",
      +  "builders",
      +  "bundle",
      +  "reval",
      +  "statement",
      +  "counterparty",
      +  "venue",
      +  "edition"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "precheck",
      -  "liveness",
      -  "paygraph",
      -  "drain",
      -  "exit",
      -  "incidents",
      -  "peer",
      -  "builders",
      -  "bundle",
      -  "reval",
      -  "statement",
      -  "counterparty",
      -  "venue"
      -]New value: +[
      +  "precheck",
      +  "liveness",
      +  "paygraph",
      +  "drain",
      +  "exit",
      +  "trace",
      +  "incidents",
      +  "peer",
      +  "builders",
      +  "bundle",
      +  "reval",
      +  "statement",
      +  "counterparty",
      +  "venue"
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "precheck",
      -  "liveness",
      -  "paygraph",
      -  "drain",
      -  "incidents",
      -  "peer",
      -  "builders",
      -  "bundle",
      -  "reval",
      -  "statement",
      -  "counterparty",
      -  "venue"
      -]New value: +[
      +  "precheck",
      +  "liveness",
      +  "paygraph",
      +  "drain",
      +  "exit",
      +  "incidents",
      +  "peer",
      +  "builders",
      +  "bundle",
      +  "reval",
      +  "statement",
      +  "counterparty",
      +  "venue"
      +]
  6. Changed3 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"Agent token id, slug or wallet; for counterparty, the receiving 0x address"New value: +"Agent token id, slug or wallet; for counterparty and venue, the 0x address"
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "liveness",
      -  "paygraph",
      -  "drain",
      -  "incidents",
      -  "peer",
      -  "bundle",
      -  "reval",
      -  "statement",
      -  "counterparty"
      -]New value: +[
      +  "precheck",
      +  "liveness",
      +  "paygraph",
      +  "drain",
      +  "incidents",
      +  "peer",
      +  "builders",
      +  "bundle",
      +  "reval",
      +  "statement",
      +  "counterparty",
      +  "venue"
      +]
    • addedInput schema / properties / payto
      Added value: +{
      +  "description": "precheck only, optional: the 0x address you are about to pay",
      +  "type": "string"
      +}
  7. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, but the description adds material facts they cannot: the price band, the x402 payment flow, and the critical caveat that this tool does not pay — an x402-capable client must fetch the returned URL and retry with a signed payment after a 402. That is exactly the kind of process/authorization context annotations cannot convey. It falls short of 5 because it never says what the returned URL response body looks like or how long a quote remains valid.

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

Conciseness2/5

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

The body is a single dense chain of semicolon-delimited parentheticals spanning all 15 pack kinds — far more detail than is needed to decide to buy a quote, and much of it belongs to whichever tool actually returns the pack. The most important operational caveat ('This tool does not pay') is buried at the very end rather than front-loaded next to the price, making the definition hard to scan and easy to misuse.

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

Completeness4/5

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

With no output schema, the description carries the return-value burden and does so adequately: it states that a URL is returned and that fetching it yields HTTP 402 with the exact price plus a retry protocol. Inputs are fully documented. What is missing is post-quote behavior — quote validity window, what happens with an already-paid URL, or payment failure handling.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description meaningfully expands the enum beyond bare labels by defining what each pack contains (edition's id formats YYYY-MM/YYYY-Qn/latest and price, trace's three-hop follow, exit's 72-hour outflow windows, venue's poisoning look-alike check). It also clarifies payto's scope ('precheck only, optional') in narrative form. Minor deduction for not restating the id/agent aliasing the schema already covers.

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?

The opening clause gives a specific verb and resource: price and purchase a dated evidence pack, with concrete payment rails (x402/USDC on Base, 1 to 30 cents). It does not, however, contrast itself with plausible siblings like agent_statement, agent_books, or pay_check, even though several of its 'kind' values (statement, events) overlap semantically with those tools and could leave an agent unsure where to go for an unpurchased read.

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

Usage Guidelines3/5

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

Guidance on choosing among the 15 pack kinds is genuinely useful (e.g. precheck is 'the routine check before you pay or hire it', exit vs trace are distinguished), which is real when-to-use context. But there is no explicit statement of when to call this tool versus a free sibling (agent_statement, counterparty_preview) or a caveat that requesting a quote buys nothing beyond what the schema enum description already says.

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.