Cross-venue funding scan for every tokenized-stock perp: each ticker's funding across Lighter/Hyperliquid/Binance/Bybit, ranked by the most extreme rate, with mark price and a crowded-long/short squeeze bias. Send { limit? }. Spot the most squeezed tokenized-stock perps in one call. [x402 paid tool — price $0.05; POST /api/rh/funding-scan]
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max rows, default 15 (max 50) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries full burden. It discloses the tool is x402 paid ($0.05), mentions input (optional limit), and specifies output includes funding rates, mark price, and squeeze bias. It does not mention read-only but scanning is inherently non-destructive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences: main functionality, practical use case, and cost/endpoint. No redundant information, concise and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description adequately outlines output fields (funding per venue, mark price, squeeze bias). Includes cost and endpoint. Could mention sorting or pagination, but overall complete for a simple scan tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. The description adds minimal value beyond the schema by restating 'limit?' and not providing additional parameter meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool performs a cross-venue funding scan for tokenized-stock perps, ranking by extreme rate with mark price and squeeze bias. This distinguishes it from sibling tools like rh_perp_funding or perps_funding which are more general.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies use for spotting squeezed tokenized-stock perps but does not explicitly state when to use this tool versus alternatives. No direct comparison to siblings is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Tools are organized by domain prefix (e.g., 'crypto_', 'rh_', 'snipe_'), which helps distinguish between areas. Within each domain, they serve distinct purposes, though some overlap between domains exists (e.g., price data appears in multiple groups). Overall, an agent can navigate effectively.
All tool names follow a consistent snake_case pattern with a domain prefix and a verb_noun combination (e.g., 'compliance_risk', 'rh_stock', 'snipe_honeypot'). This makes the API predictable and easy to explore.
With 159 tools, the server is extremely large. While the broad scope of web3 and utility functions justifies many tools, the count is significantly above the typical range for a coherent toolkit, potentially overwhelming agents and increasing selection error.
The toolkit covers a wide range of web3 operations: crypto, DeFi, compliance, safety, scheduling, memory, etc. There are no obvious major gaps for its intended purpose, though some niche areas might be missing.