Skip to main content
Glama

RFWIN: provably fair winner draws

get_signal

RF Signals: price, SMA50/200, RSI(14), MACD(12,26,9), per-timeframe trend, multi-timeframe alignment and TD-style exhaustion counts (setup 9 / countdown 13). Scout (free): daily only. Analyst+: daily, weekly and monthly. Educational only, not investment advice. Free public teaser: daily timeframe only, end-of-day data delayed by one trading day. Connect /api/mcp with an API key for current data; weekly/monthly, levels, ratios and scans need the Analyst tier (paid plans).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "get_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesTicker symbol, e.g. NVDA. Call list_signal_tickers for the supported list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: end-of-day data delayed by one trading day on the free tier, tier-gated timeframes, and a required API key for current data. It omits any indication of output shape beyond the metric list, but the latency and entitlement disclosures are non-obvious and valuable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The metric inventory is front-loaded and useful, but the tail is cluttered with commercial framing, and the 'daily only' restriction is stated twice in different words (Scout free tier and free public teaser). Two sentences of entitlement text could be compressed into one.

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?

For a single-parameter read tool with no output schema and no annotations, the definition covers what is returned, freshness, and access requirements well enough to call it correctly. Only the interaction between the advertised multi-timeframe output and the absence of a timeframe parameter is left ambiguous.

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 description coverage is 100% and there is only one parameter, so the schema already fully documents the ticker and points to list_signal_tickers. The description adds nothing about the parameter, and the repeated talk of weekly/monthly timeframes implies selectable scope that the schema does not expose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and enumerates its payload precisely: price, SMA50/200, RSI(14), MACD(12,26,9), per-timeframe trend, multi-timeframe alignment, and TD setup 9 / countdown 13 counts. It is not differentiated from any sibling, but the sibling set (get_draw, draw_winners, verify_draw) is unrelated enough that confusion is unlikely.

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

Usage Guidelines3/5

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

The definition spends its guidance on entitlement tiers (free teaser = daily only, Analyst+ = daily/weekly/monthly, API key for current data) rather than on when to choose this tool over another. Availability constraints are clearly stated, but there is no explicit when-not or alternative routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources