Skip to main content
Glama

BRAINIAC Global Financial Markets & Macro Intelligence

Analyze sovereign debt maturity

macro-intelligence_sovereign-debt-maturity-analyze

Bucket supplied sovereign debt amounts by maturity window from the as-of date without inventing missing maturities. Price $0.04 USDC. POST /api/v1/macro-intelligence/sovereign-debt-maturity-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_sovereign-debt-maturity-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

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the $0.04 USDC price, the POST endpoint, that unpaid calls return 402 without running, and that missing maturities are not invented. However, it omits authentication details, rate limits, required input combinations, and any description of the response.

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?

The description is three short sentences, front-loaded with the purpose followed by pricing, endpoint, and payment behavior. It is efficient with no filler, though its brevity is notable for such a complex tool.

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 15-parameter, nested-schema tool with no annotations and no output schema, the description is materially incomplete. It explains the analysis concept and payment behavior but gives no guidance on which input modality to use, how parameters interact, or what result shape to expect.

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?

Schema description coverage is 0% across 15 top-level parameters, and the description adds meaning only for the implicitly referenced debt and as-of inputs. It says nothing about the file/csv/json/text alternatives or the many ancillary datasets (rates, tenors, releases, observations, etc.), so it does not compensate for the schema gap.

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 ('Bucket') and resource ('sovereign debt amounts by maturity window') and adds a scope qualifier ('from the as-of date'). It does not explicitly distinguish this tool from siblings such as yield-curve-analyze or country-risk-profile, so it stops short of a 5.

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?

No when-to-use or when-not-to-use guidance is given, and no alternatives are named. The only implied usage is that the caller supplies debt amounts and an as-of date.

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