Skip to main content
Glama

x402-services

by ai.firmbrain

rh_gap_radar

Overnight/weekend gap radar: while the US cash market is closed, ranks tokenized stocks by how far their 24/7 Robinhood Chain price has repriced vs the last regular-market close, with projected gap up/down at the open. Send { tickers?, limit? }. The pre-open positioning edge for tokenized-equity agents. [x402 paid tool — price $0.05; POST /api/rh/gap-radar]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax movers, default 10 (max 25)
tickersNoOptional array of tickers; defaults to a common basket

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses behavior (ranks repricing, projected gap), cost ($0.05 per call), and endpoint. No annotation contradiction.

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 efficient sentences plus a concise note. Front-loaded with purpose. Every sentence earns its place.

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?

No output schema, but description explains what the tool returns (ranking with gap up/down). Cost and endpoint included. Sufficient for a tool with optional inputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%. Description adds default and max for limit, and default basket for tickers, adding value beyond schema.

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 is a gap radar for tokenized stocks, ranking them by repricing versus the last close with projected gap up/down. This is a specific verb+resource and distinguishes from any sibling tool.

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?

States use case: 'while the US cash market is closed' and 'pre-open positioning edge'. It gives input parameters and cost info. No explicit when-not-to-use or alternatives, but context is clear.

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

All x402-services toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness4/5

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.

Resources