Skip to main content
Glama

Money Reactor — 87 paid x402 APIs via MCP

get_wallet_profile

Paid $0.10 (x402, USDC Base): on-chain wallet profile on Base — ETH balance, tx count (nonce), USDC balance, activity tier (fresh/new/active/veteran). Pre-flight counterparty 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": {
      "address": "<address>"
    },
    "name": "get_wallet_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesWallet address 0x...

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations at all, the description carries the burden and does disclose the most consequential trait: the call is paid ($0.10 via x402 in USDC on Base), plus the chain it queries. Gaps remain around failure behavior (invalid/non-Base address, payment failure) and whether the payment is charged on error, but the cost disclosure is the behavior an agent most needs before calling.

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?

One dense sentence with the cost/payment model front-loaded and the payload list immediately after; nothing is redundant. Siblings and scope are conveyed without a wasted clause.

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?

Since there is no output schema, the description correctly enumerates the returned fields, and it names the chain and price. What is missing for a paid, single-param tool is error/edge-case behavior (unpaid request, malformed address) and whether the activity tier thresholds are fixed — minor but real gaps.

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?

Single parameter with 100% schema description coverage, so the schema already documents 'address 0x...'. The description adds only the implied constraint that the address must be on Base; it adds no format or validation detail beyond that. Baseline 3 applies.

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 a specific resource ('on-chain wallet profile on Base') and enumerates exactly what the profile contains: ETH balance, tx count/nonce, USDC balance, and an activity tier with its value set. That field list distinguishes it from siblings like get_erc20_balance (single token balance) or get_usd_price (fiat conversion) without the agent needing to open the 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?

'Pre-flight counterparty check' gives a concrete use situation, which is the main routing signal an agent needs. However, it offers no explicit exclusion or named alternative (e.g. 'for a single token balance use get_erc20_balance'), so the when-not side is left to inference.

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