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

Signal Feed API: market regime for agents

get_delayed_issue

Retrieve a market-regime issue dated at least 7 days ago and verify its integrity by recomputing its hash against the issue block and public ledger—useful for testing the feed or backtesting logic.

Instructions

Free. Use to try the feed before paying, or to backtest your own logic: the issue for a date at least 7 days old (YYYY-MM-DD), with its hash recomputed and compared to the issue's integrity block and to the public ledger.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "issue_date": "<issue_date>"
    },
    "name": "get_delayed_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
issue_dateYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose meaningful traits: the call is free (no payment/credential prerequisite), the data is deliberately delayed by 7+ days, and the response includes a recomputed hash validated against both the integrity block and the public ledger. It omits error behavior for too-recent or malformed dates, but the core behavioral profile is well covered.

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?

It front-loads the cost signal ('Free.') then the use cases, then the technical spec after the colon — a sensible ordering. The single long sentence packs cost, purpose, parameter format, and verification semantics efficiently; only the layered colon construction slightly obscures the retrieval request itself.

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?

With one required parameter and an output schema covering return values, the description needn't explain response structure, and it instead spends its words on cost, the age constraint, and the integrity check. Nothing an agent needs to call this correctly is missing beyond minor error-handling details.

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 schema only offers a bare 'Issue Date' string — so the description must compensate, and it does: it specifies the YYYY-MM-DD format and the validity constraint that the date must be at least 7 days old. That is a substantial addition over the raw schema, though it does not state what happens when the constraint is violated.

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 identifies the specific resource (the issue for a given date) plus a distinguishing constraint (at least 7 days old) and the verification behavior (hash recomputed against the integrity block and public ledger). It never names the obvious counterpart get_latest_issue, so the delayed-vs-latest distinction must be inferred from the age constraint rather than stated outright.

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 try the feed before paying, or to backtest your own logic' gives concrete when-to-use scenarios, and the 7-day minimum implies when not to use it (anything recent). It stops short of explicitly routing the agent to get_latest_issue for current issues, so the exclusion stays implicit.

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