Skip to main content
Glama

RF Signals

get_signal

RF Signals daily technical read for one ticker: price, SMA50/200, RSI(14), MACD(12,26,9), trend, alignment and TD-style exhaustion counts (setup 9 / countdown 13). Free, no key: daily timeframe, delayed one trading day. Current data, levels, ratios, scans and weekly/monthly are on the paid server (https://app.rewardsfuel.com/api/mcp, rf_live_ key). Educational only, not financial advice.

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.8/5.0
Behavior3/5

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

With no annotations, the description still discloses meaningful traits: free access, no API key, daily timeframe, one-trading-day delay, and an educational-only disclaimer. It leaves out rate limits, error behavior for unsupported tickers, and response shape, so for a bare-annotation tool the disclosure is good but not full.

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?

Two dense, front-loaded sentences where the indicator list comes first and the access/timeframe caveats follow. The paid-server URL and disclaimer are long but each carries routing or compliance value; only minor trimming would be possible.

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 with no output schema, the description does the heavy lifting by naming every returned field and its time constraint. Gaps are limited to failure modes and response formatting, which are secondary for a data-read tool of this complexity.

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

Parameters2/5

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

Schema coverage is 100%, so the single ticker parameter is already fully documented, including the example NVDA and the pointer to list_signal_tickers. The description adds nothing about the parameter itself — its "ticker" mention is only scope framing, not semantics — so this sits at baseline rather than above it.

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?

States a specific verb+resource ("daily technical read for one ticker") and enumerates exactly which indicators are returned (price, SMA50/200, RSI(14), MACD, trend, alignment, TD setup/countdown). The single-ticker scope plus the pointer to list_signal_tickers makes it distinguishable from its sibling without opening a schema.

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?

Explicitly frames the tool as the free, keyless, one-day-delayed daily option and directs the agent to the paid server for current data, levels, ratios, scans and weekly/monthly. That is a real boundary condition, though it stops short of stating when this tool should NOT be used (e.g., intraday or current-price needs beyond noting the paid alternative).

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