Skip to main content
Glama

Stratalize Intelligence

Get Credit Spread Benchmark

get_credit_spread_benchmark
Read-only

Live investment grade and high yield credit spread benchmarks from FRED ICE BofA indices — OAS by rating tier, TED spread, 2s10s Treasury spread, and distress signal. Updates daily. For credit analysts and fixed income PMs. Live source. Returns HTTP 503 (no charge) if upstream source unavailable for >50% of fields. | x402 SLA: $0.10 USDC per call. Returns HTTP 503 (no charge) when upstream data sources unavailable. data_source field discloses provenance (fred_api/fred_csv/fred_mixed).

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

Input Schema

NameRequiredDescriptionDefault
rating_tierNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

With readOnlyHint/openWorldHint already declared, the description still adds real operational context: daily refresh cadence, $0.10 USDC per-call x402 pricing, HTTP 503 with no charge when upstream sources fail for >50% of fields, and a data_source provenance field (fred_api/fred_csv/fred_mixed). The main gap is that the return shape and units (e.g., basis points) are never described, and the 503/no-charge behavior is stated twice in slightly different wording.

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

Conciseness3/5

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

The tool's identity is front-loaded, but the text is padded with redundant fragments — "Live source" adds nothing, and the 503/no-charge sentence appears twice with different phrasing. The pipe-delimited x402 SLA block reads like appended boilerplate rather than integrated prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does list the returned metrics and the data_source provenance field, which is helpful. However, for a financial data tool it omits output units, response structure, and the default rating_tier behavior, leaving an agent unable to predict the payload shape.

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 0%, so the single rating_tier enum (all/ig/hy/bbb) carries no documented meaning. The description partially compensates by mentioning "OAS by rating tier" and "investment grade and high yield," which maps to the ig/hy/bbb values, but it never states the default or what "all" returns. Enum values are largely self-explanatory, keeping this at baseline.

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?

The description names the exact resource (investment grade and high yield credit spread benchmarks), the specific upstream source (FRED ICE BofA indices), and enumerates the metrics returned: OAS by rating tier, TED spread, 2s10s Treasury spread, and distress signal. That level of specificity clearly separates it from adjacent benchmarks like get_corporate_debt_benchmark or get_cre_debt_benchmark without needing to name them.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this over any other benchmark tool, and no exclusions or prerequisites. "For credit analysts and fixed income PMs" identifies an audience rather than a usage condition, and "Updates daily" describes freshness, not when to call it.

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