Skip to main content
Glama

edge-signals

wallet_nonce

Current transaction nonce for an EVM wallet on Base or Ethereum.

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

Input Schema

NameRequiredDescriptionDefault
chainNobase (default) or ethereum
addressYesWallet 0x

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden and does little: it never states that this is a read-only lookup, whether the nonce is the latest confirmed count or includes pending transactions, or what happens for an unknown address. 'Current' hints at freshness but is not defined.

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 no filler, and the chain scope is stated up front. It is arguably too terse rather than padded, but nothing in it is wasted.

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 with fully documented schema and no output schema, the definition is minimally sufficient. It still omits the semantics of the returned nonce (confirmed vs pending) and failure conditions, which matter for an agent using the value in a transaction.

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 the schema already explains 'address' (Wallet 0x) and 'chain' (base default or ethereum). The description only restates the chain options and adds no format, default, or validation detail beyond the schema, so the baseline 3 applies.

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?

Names a specific resource (current transaction nonce) and scopes it to an EVM wallet on Base or Ethereum, which distinguishes it from siblings like wallet_balances and wallet_full_bundle. It lacks an explicit verb, but 'Current ... nonce' makes the retrieval intent unambiguous.

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 guidance on when to use this tool versus wallet_full_bundle or wallet_balances, no note on which chain to pick for a given wallet, and no prerequisites. The agent must infer all routing decisions.

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