Skip to main content
Glama

Ellimist

Recession signals

data_macro_recession_signals
Read-only

Use this to answer 'are recession signals on?' in one call: Treasury yield-curve inversion (10y-2y and 10y-3m), the Sahm rule from BLS unemployment, and real 10-year and 3-month rates after CPI inflation. Each with its official source date. Data, not advice. Price: $0.01 USDC per call via x402 (no account). Not charged if it fails.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description correctly focuses on other traits: the $0.01 USDC x402 price, no account required, and no charge on failure. That billing and failure behavior is genuinely additive; it stops short of describing response shape, latency, or freshness guarantees.

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?

Front-loaded with the use case, then the component list, then the billing terms. Every sentence carries distinct information, including the short 'Data, not advice' disclaimer, with no filler or redundancy.

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 no-parameter, no-output-schema composite, the description covers what is computed, that each figure carries an official source date, and the cost model. It could say more about the response's structure or update cadence, but an agent has enough to decide to call it and interpret the results.

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 semantics to explain and the baseline of 4 applies. The description does not need to compensate for any schema gap here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific composite resource and enumerates exactly what it covers: 10y-2y and 10y-3m curve inversion, the Sahm rule from BLS unemployment, and real 10-year/3-month rates after CPI. The phrase 'in one call' distinguishes it from the granular siblings like data_macro_treasury_curve and data_macro_bls.

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?

Gives a clear triggering question ('are recession signals on?') and implies the alternative path is assembling the same picture from multiple single-source calls. It does not explicitly name the sibling tools or state when this composite would be overkill, but the usage context is unambiguous.

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.

Resources