boo-x402-mcp

Overview Schema Source Related Servers Discussions Admin

Robinhood Chain transaction lookup

rhchain_tx

Retrieve transaction details on Robinhood Chain by hash, including status, method, sender, receiver, value, fee, block, and timestamp.

Instructions

Look up a transaction on Robinhood Chain by hash: status, method, from/to, value, fee, block, timestamp.

PAID TOOL: up to $0.005 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": {
      "hash": "<hash>"
    },
    "name": "rhchain_tx"
  }
}

Input Schema

Name	Required	Description	Default
`hash`	Yes	Transaction hash (0x...).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 11, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. Mentions it's a paid tool with cost and payment mechanism, which is helpful. However, does not disclose potential limitations like rate limits, response time, or error conditions.

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?

Two concise sentences. First describes the core functionality and returned data. Second provides critical cost information. No unnecessary words.

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

Completeness5/5

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

For a single-parameter lookup tool with no output schema, the description adequately lists the expected return fields and cost. No missing context needed for usage.

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?

Input schema has 100% coverage with one parameter 'hash' described as 'Transaction hash (0x...).' The description does not add additional meaning beyond the schema, earning a baseline 3.

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?

Clearly states the tool looks up a transaction by hash on Robinhood Chain and lists the returned fields (status, method, from/to, value, fee, block, timestamp). Distinguishes from siblings like rhchain_wallet which focuses on wallet-level data.

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?

Clear context: use when you have a transaction hash to look up on Robinhood Chain. Does not explicitly state when not to use or mention alternatives, but the purpose is narrow and well-defined.

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