Skip to main content
Glama

US yield curve regime (x402)

us_macro_regime

Read-onlyIdempotent

$0.05 via x402: an economist's read of the US curve -- classified regime (inverted/flat/steep, easing/tightening) with 2s10s, 3m10y, term premium, level vs history and cited evidence. Judgment, not a rate feed.

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

Input Schema

NameRequiredDescriptionDefault
lookbackNoTrailing sessions for context, default 60
x_paymentNox402 payment payload (base64) to settle this call; omit to receive the payment terms first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), so the description is not required to restate them. It does add genuinely new behavioral context: a $0.05 x402 charge and the requirement to omit x_payment on the first call in order to receive payment terms. It also discloses the shape of the interpretation returned, which matters since there is no output schema.

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?

Two compact clauses with no filler, and the enumerated outputs are packed efficiently into a single sentence. The price is front-loaded, which is useful for an agent deciding whether to call, though it slightly displaces the purpose statement.

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?

This is a read-only analytical tool with two optional parameters and no output schema, so the description must convey return content and cost, and it does both. An agent knows what it gets, what it pays, and how to initiate payment; only the guidance on choosing it over neighboring macro tools is thin.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both lookback and x_payment are already documented in the schema, and the baseline of 3 applies. The description reinforces the payment parameter's role implicitly through the x402 pricing sentence, but adds no syntax or format detail for lookback beyond what the schema states.

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 uses a specific verb-and-resource framing ('an economist's read of the US curve') and enumerates concrete outputs: classified regime (inverted/flat/steep, easing/tightening), 2s10s, 3m10y, term premium, level vs history, and cited evidence. That is far more specific than the tool name alone. It stops short of naming a sibling to distinguish itself from, so it lands at 4 rather than 5.

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?

Usage is only implied, chiefly through the closing contrast 'Judgment, not a rate feed,' which signals the agent should pick this for interpretation rather than raw quotes. There is no explicit statement of when this is the right call versus country_economic_indicators or a rate-feed sibling, and no preconditions beyond the payment note.

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