boo-x402-mcp

Overview Schema Source Related Servers Discussions Admin

Robinhood Chain wallet snapshot

rhchain_wallet

Retrieve wallet snapshot data on Robinhood Chain: ETH balance with USD equivalent, transaction count, account type, and reputation flags. Optionally include token holdings.

Instructions

Wallet snapshot on Robinhood Chain: ETH balance (+USD), tx count, account type, scam/reputation flags, optionally token holdings (deep=true).

PAID TOOL: up to $0.01 USDC per call (x402 on Base). Paid automatically from your configured wallet.

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

Input Schema

Name	Required	Description	Default
`deep`	No	true to also return token holdings.
`address`	Yes	Wallet address (0x...).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 11, 2026

TDQS

A4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool is paid (cost up to $0.01 USDC) and explains the optional 'deep' parameter for token holdings. It does not describe rate limits or error behavior, but the read-only nature is implied.

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?

The description is two sentences long, with the first sentence conveying the core functionality and the second addressing cost. Every word adds value; no redundancy or fluff.

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?

Despite lacking an output schema, the description provides a detailed list of return data (ETH balance, USD, tx count, account type, flags). This sufficiently informs the agent of the tool's output. Minor gaps like pagination or error conditions are acceptable for a snapshot tool.

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%, with both 'address' and 'deep' documented. The description adds value by explaining 'deep=true' for token holdings, reinforcing the schema. This is adequate but does not go beyond what the schema already conveys.

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 clearly identifies the tool as providing a wallet snapshot on Robinhood Chain, listing specific data points (ETH balance, USD, tx count, account type, scam/reputation flags, and optional token holdings). It distinguishes itself from siblings like 'rhchain_wallet_score' and 'wallet_risk' by focusing on basic snapshot info.

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 description mentions the tool is paid with a cost cap, which helps set expectations, but does not explicitly state when to use this tool versus alternatives like 'wallet_risk' or 'rhchain_wallet_score'. It lacks a clear 'when-to-use' or 'when-not-to-use' context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.