Skip to main content
Glama

BRAINIAC Base Chain Data

Get address nonce

chain-data_address_nonce

Retrieve the transaction nonce for a Base Mainnet address from the public JSON-RPC endpoint. Price $0.01 USDC. POST /api/v1/chain-data/address/nonce. Unpaid calls return 402 and do not run.

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-data_address_nonce"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes
blockNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations at all, the description must carry the full behavioral burden. It does well on two fronts, disclosing the cost model ($0.01 USDC) and the failure mode (unpaid calls return 402 and do not run), but it never says what the default block is, whether the call needs auth beyond payment, whether address must be checksummed, or what the response contains. Those gaps are significant for a paid tool with zero annotation coverage.

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?

Four short, front-loaded clauses with the core action first, then price, endpoint, and payment failure. The raw route string is arguably dead weight for an agent that does not construct HTTP requests, but there is no filler or repetition.

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?

For a two-parameter read tool this covers the action, chain, cost, and payment gate, which is much of what matters. It is nonetheless incomplete because one parameter is undefined and there is no output schema to compensate, so the agent cannot tell what a returned nonce looks like or how blockNumber affects it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description should explain both parameters, but it explains neither. The optional 'blockNumber' parameter is completely unmentioned, leaving the agent with no idea whether passing it changes semantics (historical nonce vs latest), and the 'address' parameter is only implied by the phrase 'for a Base Mainnet address'.

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 states a specific verb and resource ('Retrieve the transaction nonce') and pins the scope to a Base Mainnet address, which distinguishes it from balance, code, and receipt siblings by resource alone. It stops short of explicitly contrasting itself with the nearest alternative, so it sits below a 5.

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 or when-not-to-use guidance; the agent is left to infer that this is for reading an account's pending/confirmed nonce before signing a transaction. No sibling is named as the alternative for balance or transaction-history lookups, so nothing routes the agent.

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