Skip to main content
Glama

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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real operational context beyond them: daily update cadence, a 503-with-no-charge failure mode when upstream is unavailable, x402 pricing of $0.10 per call, and a data_source provenance field. The only blemish is that the 503 behavior is stated twice in slightly different words, and the '>50% of fields' threshold is not reconciled with the unconditional restatement.

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 core scope is front-loaded in the first clause, but the text is padded with an audience line that carries little decision value and a near-duplicate restatement of the HTTP 503 no-charge behavior, plus a trailing pricing/SLA sentence that repeats the same failure mode again.

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 single optional parameter, read-only, open-world tool with no output schema, the description covers content (the specific spreads returned), freshness, provenance disclosure, cost, and failure behavior. Only the meaning of the rating_tier enum values remains unaddressed, which is the one gap an agent must fill.

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 description must carry the one parameter. 'OAS by rating tier' implies what rating_tier selects, but it never explains the enum values (all/ig/hy/bbb) or what each subset returns, leaving the agent to guess from the labels.

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 a specific resource and upstream source: 'Live investment grade and high yield credit spread benchmarks from FRED ICE BofA indices', then enumerates the outputs (OAS by rating tier, TED spread, 2s10s, distress signal). That is far more specific than a restated name, though it never explicitly distinguishes itself from near neighbors like get_corporate_debt_benchmark or get_bank_regulatory_benchmark.

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?

'For credit analysts and fixed income PMs' identifies an audience rather than a use condition, and no alternative tool or exclusion is named. An agent can infer this is the credit-spread benchmark tool, but must decide when to prefer it on its own.

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