Skip to main content
Glama

chainread__tokenreport

Live Base/Ethereum chain reads for AI agents over x402: balance, gas, nonce, block, token metadata, tx, address verdict/risk, simulation and tx preflight. GET with query params. $0.01 per paid call; free live preview at /preview. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/chainread/tokenreport

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

Input Schema

NameRequiredDescriptionDefault
hashNo0x transaction hash (for /tx, /txpreflight)
nameNoENS name (for /ens)
chainNobase or ethereum
addressNo0x address or token contract

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior3/5

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

With no annotations, the description does carry real behavioral load and does disclose useful facts: HTTP GET transport, USDC pricing on Base (eip155:8453), and the exact x402 payment location params._meta["x402/payment"]. However it says nothing about what the call returns, whether failures are charged, rate limits, or auth expectations beyond payment.

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 listing of unrelated capabilities is noise for this specific tool, and pricing is stated twice ($0.01 per paid call and again as the Price line). The content that matters — the endpoint and payment mechanics — is buried at the end rather than front-loaded.

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

Completeness2/5

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

With no annotations, no output schema, and four optional parameters, the description must define the tool's scope and return behavior; it does neither. An agent knows the cost and transport but not what a token report contains or when it beats sibling tools.

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 schema already explains that hash is for /tx and /txpreflight, name for /ens, and address is an address or token contract. The description adds no meaning about which parameter this tool actually consumes or which combinations are valid, so it stays at the baseline.

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

Purpose2/5

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

The text is a service-level catalog blurb (balance, gas, nonce, block, token metadata, tx, verdict, simulation, preflight) rather than a statement of what chainread__tokenreport does. It never pairs a verb with the specific resource this tool returns, so an agent cannot tell from the description whether this is token metadata, a risk report, or something else. Only the trailing URL hints at the actual endpoint.

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?

There is no when-to-use guidance and no routing to alternatives, despite obvious overlap candidates like chainread__token, chainread__verdict, and chainread__tx. The only conditional information given is commercial (paid call vs free /preview), not task-selection guidance.

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