Skip to main content
Glama

get_wallet_nonce

Transaction count (nonce) for a wallet address on Base mainnet.

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

Input Schema

NameRequiredDescriptionDefault
addressYes0x-prefixed 40-char hex address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully pins the scope to Base mainnet, which prevents an agent from assuming chain selection is a parameter. However, it omits the behaviorally important distinction between pending and latest/confirmed nonce, and doesn't state that the call is a side-effect-free read or what it returns at the type level.

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 short fragment with the resource and the chain scope front-loaded; nothing is wasted. It is terse to the point of being slightly clipped, but every word earns its place.

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 one-parameter read tool with no output schema, this is adequate but thin. The agent knows what it retrieves and on which chain, but not whether the nonce reflects pending or confirmed state, nor the return type, both of which matter for correct interpretation.

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% and the single parameter is fully documented as a 0x-prefixed 40-char hex address. The description adds nothing about the address format beyond the schema, but by naming the chain it clarifies that no chain/network parameter is needed. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific resource (transaction count / nonce) for a specific object (wallet address) on a specific chain (Base mainnet). The 'get' verb is implied by name and context. It does not explicitly differentiate itself from close siblings like get_eth_balance or get_token_balance, but the resource noun is distinct enough that confusion is unlikely.

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 guidance, no prerequisites, and no mention of alternatives or exclusions. An agent must infer from the name alone that this is the read path for a wallet's nonce rather than, say, a transaction lookup.

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