Skip to main content
Glama

RFWIN: provably fair winner draws

list_signal_tickers

RF Signals: list supported tickers and the latest daily bar date for each. All tiers (free included). 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

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

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral burden and discloses important context: tier availability, one-trading-day delay for free public data, API-key use for current data, and paid-tier requirements for broader features. It does not mention rate limits or error behavior, but for a zero-parameter list operation the access and freshness disclosures are substantial.

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 purpose is front-loaded and the description is compact, with each early sentence adding useful scope or access detail. The final clause about weekly/monthly, levels, ratios and scans is somewhat broader than this specific ticker-listing tool, but it remains relevant pricing context.

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?

For a simple zero-parameter list tool with no output schema, the description states what is returned, the latest daily bar date included, data freshness limitations, and tier/API-key requirements. That is enough for an agent to understand whether and how to call it.

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 is 4. The description does not need to explain parameter usage and appropriately focuses on output scope and access conditions instead.

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 uses a specific verb and resource: "list supported tickers and the latest daily bar date for each." It clearly distinguishes the tool from retrieval-style siblings such as get_signal by focusing on ticker discovery and bar-date metadata.

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?

It gives clear access guidance: all tiers including free, daily-only delayed data for the public teaser, and API-key connection for current data. It also states that weekly/monthly, levels, ratios and scans require the Analyst tier, though it does not explicitly route to sibling tools.

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