Skip to main content
Glama

Wallet history

wallet_history
Read-only

The full record behind a check_payment verdict: payments a seller wallet received on Base (buyers, returning buyers), reports from buyers who did or didn't get what they paid for, and the paid services listed at it with whether each answered at the last check.

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": {
      "wallet": "<wallet>"
    },
    "name": "wallet_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesThe wallet address: 0x, or a Solana address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / wallet / description
      Previous value: -"The 0x wallet address."New value: +"The wallet address: 0x, or a Solana address."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value by enumerating what record categories come back, but it is silent on result volume, pagination, staleness ('last check' timing), and behavior for wallets with no history.

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?

A single dense sentence with the relationship to check_payment front-loaded and the three record categories following. No filler, no restatement of the title.

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 carries the burden of describing returns and does so by listing the record categories, which is sufficient for an agent to know what to expect. Only freshness/timing and result-size behavior are missing, and neither blocks correct invocation.

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% and the schema already explains that the wallet may be 0x or a Solana address. The description adds only the nuance that this is a seller wallet, which is marginal meaning beyond the schema — baseline 3 is appropriate.

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 description names the specific resource — the full record behind a check_payment verdict — and enumerates its contents (payments received on Base, buyer reports, paid services with answered status). It distinguishes itself from check_payment by casting itself as the detail layer beneath that verdict, though it uses a noun phrase rather than an explicit verb like 'retrieve'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'behind a check_payment verdict' implies this is the drill-down used after check_payment returns a summary, which is useful implicit routing. There is no explicit when-to-use/when-not statement and no mention of prerequisites such as whether the wallet must be registered or the seller must have activity.

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