Skip to main content
Glama

Technical signals and their historical returns

get_signals
Read-only

Returns the rule-based technical signals logged on the tracked companies, newest first: limit keeps the most recent, window gives the sessions they span, how many the log holds (total) and since when. With a scorecard of what each signal type returned when replayed over five years (after 1, 5 and 20 sessions, against SMH). Use it for recent technical signals or how a signal type has performed.

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": "get_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoSignals to return, the most recent (default 20, max 50).
symbolNoTicker. Omit for the whole universe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Signals to return (default 20, max 50)."New value: +"Signals to return, the most recent (default 20, max 50)."
  2. Changed2 schema fields changed
    • addedInput schema / properties / limit / maximum
      Added value: +50
    • addedInput schema / properties / limit / minimum
      Added value: +1
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld=false/destructive=false, so the bar is lower; the description still adds useful behavior — result ordering (newest first), the bounded log (`total`), and that the scorecard replays five years of returns after 1, 5 and 20 sessions against SMH. It does not state permission or rate/coverage limits, which keeps it from a 5.

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 sentences with the core action and ordering front-loaded. The middle clause ('`window` gives the sessions they span ... and since when') mixes return-field names into what reads like a parameter list, adding mild ambiguity without much payoff.

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?

There is no output schema, so describing the payload (signal log plus a five-year return scorecard benchmarked to SMH) is genuinely necessary and mostly done. The omission of the `symbol` scoping option and of the scorecard's shape are the remaining gaps.

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 coverage is 100%, so `limit` and `symbol` are already fully documented in the schema; the description only echoes the recency semantics of `limit`. It never mentions the `symbol` filter or the 'omit for whole universe' behavior, so it adds little beyond the schema baseline.

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?

Opens with a specific verb+resource — 'Returns the rule-based technical signals logged on the tracked companies, newest first' — which clearly separates it from siblings like get_price_history or screen_companies. The second half adds a second deliverable (a historical-return scorecard), which is clear but makes the tool's scope broader than the name implies.

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?

A single trailing sentence ('Use it for recent technical signals or how a signal type has performed') gives a use case but names no alternative tool and no exclusions. An agent must still infer whether get_price_history or screen_companies is the better entry point for related questions.

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.