stock-signal-us

evaluate_symbol

Return the bottom/top verdict for one US stock or index/ETF (e.g. NVDA, AAPL, ^IXIC, QQQ — S&P500 + major indexes covered). zone = strong_buy|buy|neutral|sell|strong_sell, score -100..+100 (bottom>0, top<0). Snapshot-based (refreshed from the flagship UsStockAI scan engine). Informational only. 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. The free pitch tool shows a live verdict for this market's showcase symbol only — this tool answers ANY symbol and adds the per-indicator breakdown behind the score.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`symbol`	Yes	US ticker, e.g. NVDA, AAPL, ^IXIC

TDQS

A4.8/5.0

Behavior5/5

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

Despite no annotations, the description fully covers behavioral traits: snapshot-based data freshness, informational nature (no investment advice), payment requirement ($0.01 per call with trial), and the exact return fields (zone and score). No contradictions.

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 front-loaded with the primary purpose, then efficiently covers zones/scores, data freshness, informational status, and payment details in 5 sentences. No waste; 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?

The description covers input, output (zone and score), data source, payment model, and sibling differentiation. Lacks explicit mention of return format structure (since no output schema), but mentions per-indicator breakdown indirectly. Minor gap.

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%, but the description adds meaning beyond the schema's 'symbol' description. It specifies 'US stock or index/ETF', gives explicit examples (NVDA, AAPL, ^IXIC, QQQ), and clarifies coverage scope (S&P500 + major indexes). This adds value.

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 a verdict (zone and score) for a single US stock or index/ETF, with explicit coverage of S&P500 and major indexes. It differentiates from the sibling tool 'pitch' by noting that pitch only shows the showcase symbol, while this tool handles any symbol and adds per-indicator breakdown.

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?

Usage guidelines are explicit: use this tool for any symbol, contrast with pitch (free but limited to showcase symbol). It explains payment flow (first call opens trial, 402 challenge with payment-signature header) and states it's informational only, helping the agent decide when to invoke.

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 tools Inspect

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

Need Help?