Skip to main content
Glama

Trading Signals Toolkit

Wallet Pay-Readiness

wallet_pay_readiness
Read-only

Before an agent pays: can this Base or Solana wallet pay a given USDC amount? Returns ETH/SOL and USDC balances, canPay for x402 (gasless for the payer) and for a direct transfer, shortfalls, USDC blacklist / frozen-account flags, wallet type (EOA, smart contract, EIP-7702) and open token approvals to well-known spenders (Base routers, Permit2, bridges) or SPL delegates (Solana), with an ok / review / cannot_pay status. Read live from public RPC. Read-only, never places orders. Informational only, not investment advice.

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

Input Schema

NameRequiredDescriptionDefault
chainNoChain (default: detected from the address format)
amountNoUSDC amount to pay (default 1)
addressYesWallet address: Base 0x… or Solana base58

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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 and destructiveHint=false, so the safety profile is redundant when the description repeats 'Read-only, never places orders.' What it does add beyond the annotations is source of truth ('read live from public RPC'), gasless x402 semantics for the payer, blacklist/frozen-account flags, and wallet-type classification. It does not address the notable idempotentHint=false on a read-only tool, which would be worth a word.

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?

Front-loaded with the decision question, then the return payload, then status values — a sensible ordering with dense, information-bearing clauses. The closing 'Informational only, not investment advice' is boilerplate that does not help an agent invoke the tool.

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?

There is no output schema, so the description correctly enumerates what comes back (balances, canPay per payment path, shortfalls, flags, wallet type, approvals, status). That covers most of the gap, but it remains silent on edge cases an agent would hit — unverified/uninitialized wallets, RPC failure behavior, and why the call is non-idempotent.

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 documents chain, amount (default 1, max 1e9), and address formats, so the schema carries the semantics. The description reinforces that the amount is USDC and that chain may be Base or Solana but adds no format or boundary detail beyond the schema. 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?

Opens with a specific decision question — 'can this Base or Solana wallet pay a given USDC amount?' — plus the exact resource (ETH/SOL and USDC balances, x402 vs direct-transfer canPay, blacklist flags, wallet type, approvals). This is far beyond a restatement of the name. It does not name a sibling tool to differentiate against, which keeps it from a 5.

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?

The framing 'Before an agent pays' gives a clear invocation context, and the status vocabulary (ok / review / cannot_pay) tells the agent how to consume the result. There are no explicit exclusions or named alternatives (e.g., versus pre_trade_check or event_gate), so the agent must infer boundaries.

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