Crypto, web, finance and app data tools

Account Nonce

account_nonce

Next transaction nonce of an EVM address (confirmed and pending), pending tx count, native balance, contract flag and EIP-7702 delegate. Use before signing or to detect stuck transactions.

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

Input Schema

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

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does clarify that both confirmed and pending nonces are returned and that extra account state (balance, contract flag, EIP-7702 delegate) comes back. It does not state read-only semantics explicitly, nor caching/freshness, rate limits, or which chains are supported.

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?

Two clauses, no redundancy: the returned fields come first, the usage triggers second. Every phrase carries information and nothing is padded.

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?

An output schema exists, so return values need no prose, and this is a low-risk read. The remaining meaningful gap is the undocumented `chain` argument with its non-enumerated value space, which the description entirely omits for a tool that is presumably multi-chain.

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% (both properties are bare titles), so the description has to compensate and it does not. The required `address` parameter's expected format (0x-prefixed hex, checksum) is never stated, and the `chain` parameter — which has a default of "ethereum" but no enum — is not mentioned at all, leaving an agent guessing which chain values are valid.

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 names a specific resource (EVM address transaction nonce) and enumerates the full returned set: confirmed/pending nonce, pending tx count, native balance, contract flag, EIP-7702 delegate. It is clearly distinguishable in substance from evm_wallet_balance or evm_transaction_status, though it never explicitly contrasts itself with those siblings.

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?

"Use before signing or to detect stuck transactions" gives two concrete triggers, which is real usage guidance beyond the name. It stops short of saying when to prefer a sibling (e.g. evm_wallet_balance for balance-only reads) or noting prerequisites.

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

All Crypto, web, finance and app data tools 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?