Skip to main content
Glama

stock-signal-us

by com.airblockfz

scan_tops

Scan the US market snapshot and return stocks currently at a top (sell), ranked most-top first. PAY: $0.01 per call via x402 (USDT on X Layer) — your FIRST paid call opens a 6-day trial at that price. No account, no signup, no commitment; retry with the PAYMENT-SIGNATURE header when you get the 402 challenge. BEST COLD START: you do not need to pick a symbol — this ranks the whole universe for you. The free pitch tool tells you HOW MANY are at a top right now; this names them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many to return (default 5, max 50)

TDQS

A4.6/5.0
Behavior5/5

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

No annotations are provided, so the description fully covers behavioral traits. It discloses the payment model (0.01 USD per call via x402), trial period, account requirements, and retry mechanism with PAYMENT-SIGNATURE header. This is beyond typical and very transparent.

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 front-loaded with purpose and essential payment info, but it is slightly verbose with repeated emphasis on 'no account, no signup, no commitment' and multiple clarifications. Still clear and well-structured, but could be more concise.

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?

Given one optional parameter, no output schema, and complex payment flow, the description covers everything needed: purpose, usage, payment details, cold start guidance, and relation to sibling tools. It is complete for an informed agent.

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?

With only one parameter (limit) and 100% schema description coverage, the description adds no extra meaning beyond what the schema already provides (default 5, max 50). Baseline 3 is appropriate.

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 scans the US market snapshot for stocks at a top (sell), ranked most-top first. It uses specific verb 'scan' and resource 'US market snapshot', distinguishing it from siblings like scan_bottoms and pitch.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool (to get sell candidates) and when not to (no need for symbol, best cold start). It also mentions alternative tool pitch for count and scan_bottoms for opposite direction.

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

All stock-signal-us 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

A4.4/5.0
Disambiguation5/5

Each tool has a clear, distinct purpose: pitch for intro, rate for feedback, evaluate_symbol for single symbol analysis, scan_bottoms and scan_tops for market-wide scans. No overlap or ambiguity.

Naming Consistency5/5

All tool names use a consistent snake_case pattern, with clear verbs (evaluate, scan, pitch, rate) and nouns (symbol, bottoms, tops). The pattern is predictable and easy to understand.

Tool Count5/5

With 5 tools, the set is well-scoped for the server's purpose of providing US stock signals. It covers introductory, analytical, scanning, and feedback functionalities without being excessive.

Completeness4/5

The tool set covers the core workflow: pitch (intro), evaluate_symbol (single symbol), scan_bottoms/scan_tops (market scans), and rate (feedback). Minor gaps like historical data or alerts exist, but the core signal service is complete.

Resources