Skip to main content
Glama

AutoPay

wallet

Base wallet snapshot: ETH and USDC balance, nonce, contract check, optional ERC-20 balance ($0.01, synchronous, charged only on success). Pay with X-PAYMENT (x402 USDC on Base) or a prepaid API key.

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

Input Schema

NameRequiredDescriptionDefault
tokenNo
addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses price ($0.01), execution mode (synchronous), billing policy (charged only on success), and the two auth/payment paths (X-PAYMENT x402 USDC on Base or a prepaid API key). It stops short of error/failure behavior, rate limits, or confirming the operation is strictly read-only.

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 operation and its payload before cost/payment details. Dense but every clause carries information; only the payment clause is slightly compressed enough to be cryptic without x402 familiarity.

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

Completeness3/5

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

For a tool with no annotations, no output schema, and zero schema description coverage, the definition covers outcome contents and billing well but omits address/token input formats and failure semantics. Adequate to invoke, incomplete for edge cases.

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 0%, so the description must compensate for two undocumented params. It partially does by tying "optional ERC-20 balance" to the optional token parameter, but neither the address format nor the token's expected form (contract address vs symbol) is specified, leaving a meaningful gap.

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?

"Base wallet snapshot" gives a specific verb+resource immediately, and the sentence enumerates the exact contents (ETH and USDC balance, nonce, contract check, optional ERC-20 balance), so an agent knows precisely what it gets back. It does not explicitly contrast itself with the supplied siblings (fetch, verify, search), which keeps it at 4 rather than 5.

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?

Usage context is implied rather than stated: "optional ERC-20 balance" tells the agent that supplying a token changes scope, and the payment sentence frames the cost/payment precondition. There is no explicit when-to-use or when-not-to-use guidance relative to alternatives, so the agent must infer the selection criteria.

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