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

Signal Feed API: market regime for agents

get_latest_issue

Retrieve today's five rule-based market-regime labels before sizing or gating a trade, with receipt, settlement transaction, and ledger hash check included. Paid per call via x402.

Instructions

Paid, 0.04 USDC on Base via x402. Use once a day when you must decide whether markets are risk-on or risk-off before sizing or gating a trade: today's five rule-based regime labels, paid from the wallet configured in this server (optionally checked first by Agent Trust preflight). Returns the issue, the receipt, the settlement transaction and the hash check against the public ledger.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

With no annotations supplied, the description carries the full burden and does well: it discloses the price and chain (0.04 USDC on Base via x402), that payment comes from the server-configured wallet, and that an Agent Trust preflight check is optional. It omits failure behavior — what happens if the wallet is unfunded, whether a second call the same day is charged again, or how settlement errors surface — which matters for a paid call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact clauses with no filler: cost and rail first, then the decision context and cadence, then the return payload. The parenthetical about Agent Trust preflight is the only incidental material and it is still operationally relevant.

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 paid call with an output schema present, the definition covers the commercial model, wallet source, cadence and trigger — everything needed to decide and invoke. The remaining gap is operational edge cases around payment and repeat calls, which an agent would want before committing USDC.

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 description correctly implies the request is parameterless by framing the call as fetching a fixed daily issue.

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 specific resource: today's five rule-based regime labels indicating risk-on vs risk-off, plus the receipt, settlement transaction and ledger hash check. That is far more than a restatement of the name. It stops short of a full 5 because it never names a sibling, leaving the boundary with get_delayed_issue and list_issues to be inferred from the word 'today's' and the 'once a day' cadence.

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?

It gives an explicit trigger ('when you must decide whether markets are risk-on or risk-off before sizing or gating a trade') and a frequency constraint ('once a day'), which is genuine selection guidance rather than a bare restatement. There is no explicit when-not condition and no named alternative for historical or per-issue data, so it falls short of a 5.

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