Skip to main content
Glama

recession_risk_v1

🔒 PREMIUM (not available anonymously on this endpoint): [EVIDENCE v1.1] US recession indicators as evidence only. Returns reason_codes (yield curve state, GDP trend, unemployment trend), signal_strength, risk_band. Rebuilt from retired macroracle in v1.1 evidence-only form — NO recession probability as label, NO LOW_RISK/HIGH_RISK classification.

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": "recession_risk_v1"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 an authentication/paywall constraint, enumerates the returned fields, and — unusually valuable — states what the tool deliberately does NOT return (no probability, no LOW_RISK/HIGH_RISK band). Missing are data freshness/cadence, the scale or units of signal_strength and risk_band, and any failure behavior for anonymous callers.

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?

Front-loaded with the access restriction, then purpose, then output fields, then negative constraints — a sensible order for an agent scanning it. Some versioning noise ('[EVIDENCE v1.1]', 'Rebuilt from retired macroracle in v1.1') consumes space without helping selection, though the 'NO X, NO Y' clauses earn their place.

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?

With no annotations, no parameters, and no output schema, the description is the only source of truth, and it covers access requirements, output shape, and scope limitations. It is slightly short on operational detail — refresh cadence, value ranges for signal_strength/risk_band, and what an anonymous caller actually receives — for a premium macro endpoint.

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 no parameter meaning to explain and the baseline applies. The description's field list describes outputs, not inputs, and correctly does not invent parameters.

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 specific resource (US recession indicators) and enumerates the concrete return fields (reason_codes, signal_strength, risk_band), which lets an agent picture the output before calling. It also distinguishes itself semantically from classification tools by insisting on 'evidence only' and explicitly disclaiming a recession probability label. It stops short of naming which sibling (yield_curve, market_stress_v1, macro_dashboard) it replaces or overlaps with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives an access prerequisite ('PREMIUM, not available anonymously') and an implicit usage constraint ('evidence only, no classification'), which tells the agent this is for raw indicator evidence rather than a risk verdict. It never states when to prefer this over yield_curve or market_stress_v1, which cover overlapping subject matter, so routing between siblings remains guesswork.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.