Genexxis paid agent tools (x402)

chainread_read_contract

Call any view/pure function with a human-readable signature on Ethereum, Base, Arbitrum, Optimism, Polygon or BSC: decoded result, raw hex, block number, chain id; 422 with revert reason on revert. Price: $0.003 USDC per call, paid with x402 on Base.

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": {
      "address": "<address>",
      "function": "<function>"
    },
    "name": "chainread_read_contract"
  }
}

Input Schema

Name	Required	Description
`args`	No	Arguments in order; integers may be strings
`chain`	No	ethereum (default), base, arbitrum, optimism, polygon, bsc or chain id
`address`	Yes	Deployed contract address (0x...)
`blockTag`	No	latest (default), safe, finalized, earliest, pending or a block number (alias: block)
`function`	Yes	Human-readable signature, e.g. "balanceOf(address) view returns (uint256)"; the "function " prefix is optional; include returns (...) to decode

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the return payload (decoded result, raw hex, block number, chain id), the failure mode (HTTP 422 with a revert reason), and the commercial/auth requirement ($0.003 USDC per call via x402 paid on Base). It omits rate limits, caching, and whether reads ever require an API key beyond the x402 payment.

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

Conciseness5/5

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

A single front-loaded sentence leads with the action and scope, then appends the return shape, error behavior and price as trailing clauses. Nothing is redundant and no sentence fails to earn its place.

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?

There is no output schema, and the description compensates by naming the returned fields, which is exactly what an agent needs to parse the response. For a 5-parameter paid read tool the picture is nearly complete, missing only guidance on choosing this tool over chainread_multicall for multiple reads.

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 every parameter (args, chain, address, blockTag, function) is already documented, including chain names, blockTag aliases and signature format. The description's mention of the chain list and readable signature format largely restates the schema rather than adding meaning; baseline 3 applies.

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 states a specific verb and resource — call any view/pure contract function on a named set of six chains — and scopes it to read-only calls, which distinguishes it from chainread_multicall (batched), chainread_token (token-specific) and chainread_resolve. An agent can pick this tool without opening the schema.

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?

The 'view/pure function' qualifier gives clear usage context and implicitly excludes state-changing calls, which is the key when-to-use condition for a contract-read tool. It never names an alternative for batching multiple reads (chainread_multicall) or for token/address lookups, so routing among siblings is left partly to inference.

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

All Genexxis paid agent tools (x402) 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?