Agent Data Tools: Chain data

by dev.workers.revmesh2074.agent-data-tools

Network info, Base and USDC: Base network facts for payment clients: chain id, USDC contract, RPC and explorer URLs

network

Read-only

Reference facts for paying and reading on Base mainnet: chain id, native USDC contract and decimals, block explorer and public RPC URLs, and the x402 network identifier. Use to configure an x402 or Base client. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

Input Schema

Name	Required	Description	Default
`only`	No	Optional: comma-separated top-level result keys to keep, for a smaller answer (for example only=price,symbol); unknown keys are ignored and an empty match returns the full result

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

changedInput schema / properties / only / description

Previous value: -"Optional: comma-separated top-level result keys to keep, for a smaller answer (for example only=fastestFee,halfHourFee); unknown keys are ignored and an empty match returns the full result"New value: +"Optional: comma-separated top-level result keys to keep, for a smaller answer (for example only=price,symbol); unknown keys are ignored and an empty match returns the full result"

Changed1 schema field changedOct 20, 2026

addedInput schema / properties / only

Added value: +{
+  "description": "Optional: comma-separated top-level result keys to keep, for a smaller answer (for example only=fastestFee,halfHourFee); unknown keys are ignored and an empty match returns the full result",
+  "type": "string"
+}

First observedOct 18, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond the annotations it discloses cost per call ($0.01), that failed calls are free, that the first 25 calls are free, and that repeats are charged — valuable context an agent cannot infer from readOnlyHint/destructiveHint. It also explicitly states the tool changes nothing, reinforcing readOnlyHint without contradicting it. It says nothing about response shape or the odd idempotentHint=false, leaving that hint unexplained.

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?

The returned fields are front-loaded in the first clause, followed by the use case and then pricing. Sentences are dense but each contributes; only 'Reads or computes only and changes nothing' is mildly redundant against the readOnlyHint annotation.

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

Completeness5/5

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

For a one-optional-parameter, no-output-schema reference tool, the description covers what is returned, why to call it, and the billing model. Nothing an agent needs in order to decide to call it and to expect the cost is missing.

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?

The single parameter 'only' is fully documented in the schema (100% coverage) and the description adds nothing about filtering behavior. Baseline 3 applies when the schema already carries the parameter semantics.

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

Purpose5/5

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

The description gives a precise verb-plus-resource statement: static reference constants for Base mainnet, enumerated explicitly (chain id, native USDC contract and decimals, explorer and RPC URLs, x402 network identifier). This clearly separates it from the many sibling tools that perform live chain queries (base_block, base_token_info, base_gas), which return mutable state rather than fixed configuration facts.

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

Usage Guidelines4/5

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

It names a concrete use case ('Use to configure an x402 or Base client') and explains the payment paths (x402 USDC or card key via /credits, first 25 free). It does not name alternatives or state when not to use it, but the static-configuration framing makes the boundary reasonably clear.

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

All Agent Data Tools: Chain data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?