Skip to main content
Glama

USDC wallet statement

wallet_statement
Read-only

Use when you need a reconciled Base USDC statement for a bounded UTC window. Export native Base USDC wallet transfers as JSON or CSV for a past range up to 90 days, start inclusive/end exclusive. Exact decimal running balances, counterparties and OFAC flags. Up to 1000 transfers/128 RPC calls/25 seconds; oversized or unavailable historical data fails without charge. Informational, not tax advice. Price $0.05 USDC on Base. No free trial. Price: 0.05 USDC. Minimal input example: {"address":"0xBf4164e07552e4c1b1B1597E72C7acAA3F0a1c58","start":"2026-10-22T22:07:00Z","end":"2026-10-22T22:08:00Z","format":"json"}. Illustrative output excerpt: {"kind":"wallet_statement","opening_balance":"4.188374","closing_balance":"4.238374","complete":true,"rows":[{"direction":"in","amount":"0.050000","running_balance":"4.238374"}]}. Illustrative output excerpt, not a live result, signature, approval or guarantee. Freshness/data/availability checks still apply. How to pay (MCP): No shared free trial for this tool. Use an x402-capable MCP client. A generic MCP connector without payment support cannot complete a paid continuation. On payment required, STOP. Inspect the exact accepts amount, asset, network and payTo; obtain explicit wallet/budget approval before continuing. Only after approval, let the configured x402 MCP client attach its signed payload in _meta["x402/payment"] and retry the same tools/call arguments. Never send a separate USDC transfer or paste keys into tool arguments. Never silently fall back from free access to payment. If a signed attempt has an unknown outcome, inspect that authorization/transaction; do not create another automatically.

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>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "wallet_statement"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesRequired. Exclusive past end timestamp string in ISO 8601 with timezone; UTC recommended. Example: 2026-10-02T00:00:00Z. Must be later than start and not in the future.
startYesRequired. Inclusive past start timestamp string in ISO 8601 with timezone; UTC recommended. Example: 2026-10-01T00:00:00Z. Start/end window must be at most 90 days.
formatNoOptional. Output format enum string: json or csv. Example: csv. Defaults to json.json
addressYesRequired. 0x-prefixed 20-byte Base address string. Example: 0xBf4164e07552e4c1b1B1597E72C7acAA3F0a1c58.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"Required. 0x-prefixed 20-byte Base address string. Example: 0xBf4164e07552e4c1b1B1597E72C7acAA3F0a1c58."
    • removedInput schema / properties / end / $ref
      Removed value: -"#/properties/start"
    • addedInput schema / properties / end / description
      Added value: +"Required. Exclusive past end timestamp string in ISO 8601 with timezone; UTC recommended. Example: 2026-10-02T00:00:00Z. Must be later than start and not in the future."
    • addedInput schema / properties / end / format
      Added value: +"date-time"
    • addedInput schema / properties / end / type
      Added value: +"string"
    • addedInput schema / properties / format / description
      Added value: +"Optional. Output format enum string: json or csv. Example: csv. Defaults to json."
    • addedInput schema / properties / start / description
      Added value: +"Required. Inclusive past start timestamp string in ISO 8601 with timezone; UTC recommended. Example: 2026-10-01T00:00:00Z. Start/end window must be at most 90 days."
  2. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Example arguments: {\"address\":\"0x1111111111111111111111111111111111111111\",\"start\":\"2026-10-01T00:00:00Z\",\"end\":\"2026-10-02T00:00:00Z\",\"format\":\"json\"}"New value: +"Example arguments: {\"address\":\"0xBf4164e07552e4c1b1B1597E72C7acAA3F0a1c58\",\"start\":\"2026-10-22T22:07:00Z\",\"end\":\"2026-10-22T22:08:00Z\",\"format\":\"json\"}"
  3. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-idempotent, so the bar is lower, yet the description still adds real behavioral context: throughput caps (1000 transfers/128 RPC calls/25s), that oversized or unavailable data fails without charge, OFAC flags, and exact-decimal balances. The long x402 payment/approval procedure is genuinely useful but reads as boilerplate and is partly duplicated (price stated twice).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are well front-loaded and information-dense, but the body is bloated: the price is repeated ('Price $0.05 USDC on Base' and 'Price: 0.05 USDC'), and a long payment-procedure paragraph plus a full illustrative output excerpt crowd out the core description.

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?

With no output schema, the description compensates by supplying an illustrative output excerpt (kind, opening/closing balance, complete flag, rows) along with cost, limits and failure behavior. An agent has enough to call it correctly and anticipate the response shape, aside from unspecified pagination/truncation behavior for the 1000-transfer cap.

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 coverage is 100%, so the schema already documents address, start, end and the format enum, including the inclusive/exclusive semantics. The description adds only a restatement of the example arguments, 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?

The opening sentence names a specific verb and resource ('Export native Base USDC wallet transfers as JSON or CSV') plus the scope ('past range up to 90 days, start inclusive/end exclusive'). It is unambiguous and clearly distinct from the check_*/payment siblings, though it never explicitly says what it is not.

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?

'Use when you need a reconciled Base USDC statement for a bounded UTC window' gives a clear triggering condition, and the 90-day/past-only constraints define when it cannot be used. It stops short of naming alternatives or a when-not-to-use case.

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.