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

Signal Feed API: market regime for agents

get_deviations

Check whether a bad day was a data or system problem by listing dated bugs, outages, stops, and other deviations that affected an indicator's account.

Instructions

Free. Use to check whether a bad day was a data or system problem: dated bugs, outages, stops and other deviations that affected an indicator's account.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

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 must carry the behavioral burden; it does disclose cost ("Free") and the kind of records returned. It does not address access requirements, freshness, or how far back deviations are retained, and the return shape is left to the output schema.

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 short sentences, front-loaded with the cost signal and then the use case, with no wasted clauses. The phrasing "an indicator's account" is slightly vague but does not bloat the definition.

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 zero-argument read tool with an output schema, the description supplies enough — what it is for and what it returns. Only minor gaps remain around data recency and scope, which an agent could live without.

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 there is nothing for the description to disambiguate beyond what the empty schema already shows. Baseline 4 applies.

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?

States a concrete purpose — checking whether a bad day was a data or system problem — and enumerates the resource contents (dated bugs, outages, stops, other deviations). It is not a tautology of the name, though it doesn't explicitly contrast itself with siblings like get_delayed_issue or get_latest_issue.

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 to check whether a bad day was a data or system problem" gives a clear triggering scenario for the agent. There is no when-not guidance and no named alternative, so it stops short of full routing guidance.

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