Skip to main content
Glama

Base wallet holdings in USD (x402)

What a Base wallet holds: ETH plus USDC, USDbC, DAI, WETH, cbBTC, AERO and DEGEN balances with USD values and a total, r

wallet_holdings
Read-onlyIdempotent

What a Base wallet holds: ETH plus USDC, USDbC, DAI, WETH, cbBTC, AERO and DEGEN balances with USD values and a total, read live (address=0x...). For portfolio, risk and counterparty agents that need a quick holdings check without an indexer key. Pay per call $0.02 USDC on Base via x402.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wallet_holdings"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressNoEVM wallet address on Base, 0x...
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds genuinely useful behavior the annotations cannot express: a live (non-cached) read, no indexer key dependency, and a concrete pay-per-call price of $0.02 USDC on Base via x402. The two-step payment handshake is only implied here and fully documented in the x_payment parameter rather than in the description itself, so it falls short of a 5.

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?

The key information — what is returned — is front-loaded in the first clause, followed by audience and pricing. The single sentence is dense and comma-spliced rather than broken into scannable segments, which slightly hurts readability but wastes no words.

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?

For a two-parameter read tool with no output schema, the description enumerates the returned assets, the USD valuation and total, and discloses the paid x402 access model — enough to call it correctly. A one-line note on the first-call price-response behavior would make it fully self-contained.

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 both parameters are fully documented in structured data; the description only echoes the address format (address=0x...) and gestures at x402 payment. That is the expected baseline when the schema does the heavy lifting, with no meaningful added syntax or format detail.

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?

The description names the exact resource (a Base wallet's holdings), the verb (read live), the token set returned (ETH, USDC, USDbC, DAI, WETH, cbBTC, AERO, DEGEN), and the addition of USD values plus a total. An agent knows precisely what comes back without opening 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?

It states clear usage context — portfolio, risk and counterparty agents needing a quick holdings check — and a condition that selects this tool over indexer-based alternatives ("without an indexer key"). No sibling tools exist, so no explicit exclusion is required, but the when-not guidance is implicit rather than spelled out.

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