Skip to main content
Glama

RF Signals

list_signal_tickers

RF Signals: list the supported tickers (AAPL, AMZN, GOOGL, META, MSFT, NVDA, QQQ, SPY and TSLA) and the latest daily bar date for each. Free, no key. Educational only, not financial advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_signal_tickers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does disclose the relevant traits for a trivial read: no API key required, no cost, and exactly what data comes back (a ticker list with each ticker's latest daily bar date). It omits rate limits and response shape details, which is a minor gap for a zero-parameter listing.

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?

One front-loaded sentence states the action, the full ticker universe, and the return payload; two short trailing clauses cover access cost and the educational disclaimer. Nothing is padded or repeated.

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?

With no output schema and no parameters, the description supplies enough for correct invocation: it names the exact tickers returned and the accompanying field (latest daily bar date). Only the precise response structure (field names, ordering) is left unspecified, which is a small residual 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?

The tool takes zero parameters, so the baseline of 4 applies. The description correctly implies no input is needed by framing the call as a plain enumeration of a fixed ticker set.

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 states a specific verb and resource ('list the supported tickers') and even enumerates the exact ticker set plus the per-ticker payload ('latest daily bar date for each'). It does not explicitly distinguish itself from the sibling get_signal, but the read-only enumeration scope is unmistakable.

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?

Usage is implied rather than stated: an agent can infer this is the discovery step before calling get_signal for a specific ticker, but the description never names that alternative or says when not to use this tool. The 'Free, no key' note is useful practical context but not routing guidance.

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