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

Signal Feed API: market regime for agents

get_catalog

Retrieve daily regime label definitions, exact indicator rules, schedule, pricing, issue dates, and access tiers before trusting signals. Returns a free catalog with timestamp proofs and the full paper results record.

Instructions

Free. Use first, when you need to know what the daily regime labels mean before trusting them: indicators and their exact rules, schedule, price, latest and first issue dates, free and paid access, timestamp proofs and the results record.

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

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 supplied, the description carries the burden alone; it does disclose that the call is 'Free', which is genuine cost/auth context an agent cannot get elsewhere. It does not state explicitly that this is a read-only, side-effect-free metadata lookup, nor anything about rate limits or freshness of the catalog itself.

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 ordering instruction and the free-cost fact are front-loaded in two short fragments before the content list. The enumerated payload items are dense but each adds information; the only weakness is that the list runs on without grouping.

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-parameter tool with an output schema already declaring the return shape, the description covers what the agent needs: what the catalog contains and why to consult it first. The one gap is sibling differentiation against get_schema, which the agent must resolve on its own.

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 and the baseline of 4 applies. The listed content areas describe the payload rather than arguments, which is appropriate here.

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 the resource concretely: a catalog of the daily regime's indicators, their exact rules, schedule, price, issue dates, access tiers, timestamp proofs and results record. That is far more specific than the generic name 'get_catalog'. It stops short of distinguishing itself from the sibling get_schema, so an agent must infer which metadata source to prefer.

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 first, when you need to know what the daily regime labels mean before trusting them' gives an explicit ordering and a triggering condition. What is missing is any exclusion — nothing tells the agent when get_schema or get_results_record is the better call instead.

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