Skip to main content
Glama

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

crypto_state_attestation

[$0.05] Anchor any EVM address or contract to a live RPC block header, stateRoot, and SHA-256 state commitment cached in SQLite for downstream agent verification.

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": "crypto_state_attestation"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoTarget chain ('base' or 'ethereum')base
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
ttl_secondsNoAttestation cache TTL in seconds (default 120)
subject_addressNoTarget EVM address or contract to attest (0x...)

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?

With no annotations, the description carries the full burden, and it does disclose two real behavioral traits: a $0.05 cost and that results are cached in SQLite (TTL behavior is only in the schema). It does not state that the operation is read-only/non-mutating, what happens on unsupported chains or RPC failure, or how the 'degraded' fast path manifests beyond the schema note.

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 front-loaded sentence with the price tag leading and the output artifacts before the use case; no filler. It is dense rather than padded, though the bracketed price prefix is slightly noisy.

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?

There is no output schema, so the description should fully convey what comes back; it names the block header, stateRoot and SHA-256 commitment, which is good, but leaves the response envelope and the degraded-mode result shape unexplained. For a 4-parameter, unannotated tool with a paid call, additional behavioral detail would be warranted.

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%, including the timeout_ms degraded-mode semantics and ttl_seconds, so the schema already does the heavy lifting and the baseline of 3 applies. The description adds only marginal meaning, mainly that the subject can be an address or a contract and that caching is involved.

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 description uses a specific verb ('Anchor') plus a precise resource set ('any EVM address or contract to a live RPC block header, stateRoot, and SHA-256 state commitment'), so an agent knows exactly what the tool produces. It does not name or contrast with any sibling (e.g. crypto_zk_receipt_verify or agent_preflight), so the differentiation element is absent.

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 only usage cue is the trailing phrase 'for downstream agent verification', which implies context but never states when to call this versus alternatives or what prerequisites must hold. There are no exclusion conditions, no ordering guidance, and no mention of how it relates to the other crypto/agent tools.

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