boo-mpp-mcp

Robinhood Chain transaction lookup

rhchain_tx

Fetch Robinhood Chain transaction details by hash: status, method, from/to, value, fee, block, timestamp. Pay per call via MPP with USDC.e.

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.e per call (MPP on Tempo). 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.1Aug 6, 2026

TDQS

A4.2/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 of behavioral disclosure. It transparently reveals the cost (up to $0.005 per call) and the return fields, adding context beyond the schema. It does not mention edge cases like not-found behavior, but for a read-only lookup the disclosed information is substantial.

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 concise sentences: the first states the purpose and return data, the second states the pricing. Every word earns its place, with no filler or repetition. The structure is front-loaded with the primary action.

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?

For a single-parameter tool without an output schema, the description lists the expected output fields and the cost, which covers the essential context. It does not address error handling or not-found cases, but overall it is sufficiently complete for such a simple lookup 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 description coverage is 100%, with the parameter 'hash' already described as 'Transaction hash (0x...).' The tool description adds no further semantic detail beyond what the schema provides, so the baseline of 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 clearly states the verb 'Look up' and the resource 'transaction on Robinhood Chain', and enumerates the specific data fields returned (status, method, from/to, value, fee, block, timestamp). This distinguishes it from sibling tools like rhchain_wallet or rhchain_token_screener, which serve different purposes.

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 description sets a clear context by specifying that this is for querying a transaction by hash, and it also notes the tool is paid, which is a relevant usage consideration. However, it does not explicitly name alternatives or state when NOT to use it, though sibling names provide some implicit guidance.

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