Skip to main content
Glama

get_wallet_summary

Composite read: returns ETH balance, USDC balance, nonce, latest block, and gas price for any wallet in ONE call (5 RPC reads executed in parallel). Replaces 5 separate tool calls — 5x faster, 5x cheaper than calling individual tools.

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

Input Schema

NameRequiredDescriptionDefault
addressYes0x-prefixed 40-char hex wallet address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations supplied, the description does real work: it declares this a read operation, discloses the underlying implementation (5 RPC reads in parallel), and quantifies the cost/latency tradeoff versus the granular tools. It omits failure semantics — e.g. whether one failing RPC read fails the whole composite response — which matters for an unannotated tool.

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?

Two sentences, front-loaded with the returned fields and followed by the efficiency rationale. '5x faster, 5x cheaper' is slightly redundant marketing phrasing that restates the same benefit twice, but it stays short and readable.

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?

There is no output schema, so the description's enumeration of the five return values is essential and present. For a composite read with one simple parameter and no annotations, that covers what an agent needs to select and invoke it; only error/partial-failure behavior is left unstated.

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

Parameters4/5

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

Only one parameter at 100% schema coverage, so the schema already documents the 0x-prefixed 40-char hex format. The description adds scope meaning ('for any wallet'), clarifying no ownership or connection restriction applies. Baseline for a fully-covered single param is met.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Composite read') and enumerates exactly what comes back: ETH balance, USDC balance, nonce, latest block, gas price. The claim that it replaces 5 separate calls implicitly distinguishes it from the granular siblings (get_wallet_nonce, get_eth_balance, get_gas_price, get_block_number) without the agent needing to open any schema.

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?

Clear context for use — call once instead of five times when you need the full wallet picture, valid 'for any wallet'. It stops short of stating the inverse case (when a single-field tool is preferable, e.g. if you only need the nonce) and gives no prerequisite or exclusion guidance.

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