AgentReader

chain_nonce

Next transaction nonce for any address (latest and pending) via eth_getTransactionCount — how many txs it has sent, and whether one is stuck in the mempool. Example: {address:"0xd8dA…6045", chain:"base"}. $0.001 USDC.

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>"
    },
    "name": "chain_nonce"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	No
`wallet`	No
`address`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026
- addedInput schema / properties / wallet
```
Added value: +{
+  "type": "string"
+}
```
AddedNov 5, 2026

TDQS

A3.6/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; it does disclose the upstream RPC method and a hard cost ($0.001 USDC), which is real behavioral value. However, it says nothing about which chains are supported, default chain behavior, error cases for an invalid address, or rate limits — gaps that matter for an unannotated paid tool.

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 purpose, a clarifying gloss, an inline example, and the price — dense but earned. The example adds some clutter relative to its informational value, keeping it below the top mark.

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?

With three params (one required), no output schema and no annotations, the description conveys what the number means but not the shape of the 'latest and pending' response. The undocumented 'wallet' parameter and unstated chain coverage leave material gaps for correct invocation.

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 0%, so the description must compensate, and it only partly does: 'address' and 'chain' are illustrated by the example, but the third parameter 'wallet' is never explained or distinguished from 'address'. No default chain or address format is stated.

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?

States a specific verb+resource — the next transaction nonce for any address, returned for both latest and pending — and pins it to eth_getTransactionCount so the agent knows the underlying semantics. The phrase 'how many txs it has sent, and whether one is stuck in the mempool' makes it distinguishable from siblings like chain_balance or tx_status.

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?

Usage context is implied ('whether one is stuck in the mempool') but there is no explicit when-to-use or when-not guidance and no named alternative such as chain_pending or tx_status. The agent must infer which sibling answers nonce/mempool questions.

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

All AgentReader 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?