Skip to main content
Glama

edge-signals

wallet_full_bundle

Wallet bundle: ETH + USDC balances, nonce, and live gas fees in one paid call.

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

Input Schema

NameRequiredDescriptionDefault
addressYesWallet 0x

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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, and it does disclose two behavioral facts: the call is paid (cost consequence) and the gas data is live (freshness). It does not state that it is a read-only lookup with no signing, nor what happens on an invalid or non-existent address.

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?

One dense, front-loaded sentence with no filler; the enumeration of returned data is the most useful possible content for the word count.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Absent an output schema, the description usefully enumerates the four returned values, which is the main thing an agent needs to plan around. For a one-parameter, annotation-free read tool only minor gaps remain (chain scope, failure behavior).

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?

There is a single required parameter with 100% schema description coverage, so the schema already documents 'address'. The description adds nothing about the address format or accepted chains beyond what the schema shows, so 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 concrete composite resource and enumerates exactly what it returns: ETH balance, USDC balance, nonce, and gas fees. That enumeration implicitly separates it from the single-purpose siblings wallet_balances and wallet_nonce, though the description never names them.

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?

The phrase 'in one paid call' hints at a cost/batching tradeoff versus separate calls, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must infer that this replaces several individual calls.

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