boo-x402-mcp

by lucle87

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

Robinhood Chain trending tokens

rhchain_trending

Identifies trending meme and community tokens on Robinhood Chain by 24h volume. Optionally includes stock tokens.

Instructions

Trending tokens on Robinhood Chain by 24h volume: meme/community tokens pumping now. Stock Tokens excluded unless includeStock=true.

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rhchain_trending"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Max results.
`includeStock`	No	true to include tokenized Stock Tokens.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 11, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses that the tool is paid with specific cost and payment method, but lacks information on rate limits, idempotency, data freshness, or destructive nature (implied read-only).

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?

The description is two sentences covering purpose and pricing. The first sentence could be slightly more concise, but overall it is efficient and front-loaded with key information.

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?

For a simple list tool with no output schema, the description covers purpose and pricing. However, it does not hint at return structure (e.g., if results include volume or just token symbols) or sort order, leaving some 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?

Schema covers 100% of parameters, baseline 3. The description adds context for 'includeStock' (default false) but does not add constraints or format for 'limit'. It provides some added meaning but not substantial.

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 it returns trending tokens by 24h volume, focusing on meme/community tokens, and distinguishes itself from siblings by specifying exclusion of Stock Tokens unless includeStock=true.

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 clearly indicates when to use (trending tokens by volume, meme/community tokens pumping now) and includes paid tool details. It does not explicitly exclude alternatives or state when not to use, but the purpose is well-defined.

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