Skip to main content
Glama
Signal Feed API: market regime for agents

Signal Feed API: market regime for agents

get_results_record

Review full daily paper-trading results for each indicator—losses, fees, drawdown, and benchmark exposure—to decide how much weight to give an indicator.

Instructions

Free. Use when deciding how much weight to give an indicator: full daily PAPER results of the virtual account behind each one (equity, return, benchmark, exposure, flat days, weekly fees and drawdown), losses included. Optional indicator id filter. Not real-money results.

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_results_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
indicatorNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 load and does real work: it discloses that the results are simulated ('PAPER', virtual account), that losses are included (not a cherry-picked winning subset), the granularity (daily), and the metric set including fees and drawdown. What it omits is read-only status, whether output is paginated, and any auth or rate constraints — meaningful gaps for a tool with zero annotation coverage, but the data-provenance disclosure is unusually strong.

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?

Three compact sentences, front-loaded with the cost signal 'Free' and the usage trigger before the content enumeration. The parenthetical metric list is long but each item is informative rather than filler. Minor cost: the metric list sits mid-sentence and could be trimmed without losing selection value.

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?

An output schema exists, so return structure needn't be spelled out, and the description instead supplies the semantics an agent needs — data provenance, metric coverage, and the optional filter. For a single-parameter read tool this is close to complete; the remaining unknown is whether an unfiltered call returns all indicators at once or requires an id.

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?

Schema coverage is 0% — the parameter only carries the title 'Indicator' and a nullable string type. The description compensates by stating it is an optional filter on indicator id, which tells the agent both that omission returns a broader set and what key it accepts. It does not state what happens across multiple indicators or the id format, so it stops short of fully closing the schema gap.

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 concrete resource and enumerates its contents: daily paper results of the virtual account behind an indicator (equity, return, benchmark, exposure, flat days, fees, drawdown). The closing note 'Not real-money results' sharpens what the data actually is. It does not explicitly contrast with any sibling, but none of the listed siblings (catalog, issues, disclosures, deviations) is a plausible substitute, so ambiguity risk is low.

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?

'Use when deciding how much weight to give an indicator' gives a clear decision context rather than a generic 'retrieve results'. There is no when-not guidance and no named alternative, which keeps it below a 5, but the stated use case is specific enough to route an agent reliably.

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