Skip to main content
Glama

BRAINIAC Global Financial Markets & Macro Intelligence

Analyze yield curves

macro-intelligence_yield-curve-analyze

Analyze supplied sovereign yield tenors for slope, curvature, and curve shape without inventing missing points. Price $0.05 USDC. POST /api/v1/macro-intelligence/yield-curve-analyze. Unpaid calls return 402 and do not run.

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": "macro-intelligence_yield-curve-analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
debtNo
fileNo
jsonNo
textNo
ratesNo
eventsNo
seriesNo
tenorsNo
releasesNo
worldBankNo
commoditiesNo
priceLevelsNo
observationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose operationally critical behavior: a $0.05 USDC charge, the POST endpoint, and that unpaid calls return 402 and do not execute. It also states the no-fabrication guarantee about missing points. What it omits is response shape and error behavior beyond 402, and there is no output schema to cover that.

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?

Three short sentences, front-loaded with the analytical purpose before the pricing and transport details. Every sentence carries distinct information: capability, cost, endpoint, and failure mode. Nothing is redundant with the title.

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

Completeness2/5

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

For a tool with fifteen optional inputs, deeply nested objects, no annotations, and no output schema, the description is far too thin. It does not tell the agent which input family is the primary path, what happens if all inputs are omitted, or what the result structure contains, leaving most of the calling decision undocumented.

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

Parameters2/5

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

Fifteen parameters with 0% schema description coverage and no enums means the description must explain the inputs, and it effectively explains none. It references 'tenors' in prose but never clarifies whether to pass the `tenors` array, `rates`, `observations`, `csv`, `json`, `text`, or `file`, nor how the many unrelated-looking arrays (debt, events, commodities, worldBank) relate to a yield-curve analysis.

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 verb ('Analyze'), a specific resource ('supplied sovereign yield tenors'), and the exact analytical outputs (slope, curvature, curve shape), so an agent knows what it gets back conceptually. It stops short of explicitly contrasting itself with near neighbors such as sovereign-debt-maturity-analyze or central-bank-rate-compare, leaving the boundary to be inferred from the word 'yield'.

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?

'Supplied ... without inventing missing points' implies the caller must provide tenor data and that the tool will not fetch or interpolate on its own, which is real usage guidance. However, there is no explicit when-to-use versus when-to-use-a-sibling statement and no guidance on what to do when no inputs are given, even though zero parameters are required.

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