Skip to main content
Glama

BondTerminal

Riesgo país

bondterminal_riesgo_pais
Read-onlyIdempotent

Return the current Argentina country-risk spread and deltas, with optional history. YTM conventions are percent, spreads are basis points, and bond prices are per 100 face. Explicit history is capped at 730 days and 750 returned points. Billing: current snapshot is free; including history costs 1 read unit.

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

Input Schema

NameRequiredDescriptionDefault
endNoLast day, YYYY-MM-DD. Needs start; at most 730 days after it.
rangeNoNamed window: 1w, 1m, 3m, ytd, 1y or 2y. start and end replace it when both are given.1y
startNoFirst day, YYYY-MM-DD. Needs end.
include_historyNoAlso return daily history for range, or for start and end.

Output Schema

NameRequiredDescriptionDefault
urlNoThe riesgo país page on bondterminal.com.
dateYes
deltasYes
historyNo
spreadBpsYes
lastUpdatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / end / description
      Added value: +"Last day, YYYY-MM-DD. Needs start; at most 730 days after it."
    • addedInput schema / properties / include_history / description
      Added value: +"Also return daily history for range, or for start and end."
    • addedInput schema / properties / range / description
      Added value: +"Named window: 1w, 1m, 3m, ytd, 1y or 2y. start and end replace it when both are given."
    • addedInput schema / properties / start / description
      Added value: +"First day, YYYY-MM-DD. Needs end."
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description still adds substantial context: YTM in percent, spreads in basis points, prices per 100 face, plus hard limits on history size and the billing model. That is exactly the kind of non-schema behavioral detail this dimension rewards.

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 sentences, each carrying distinct information: purpose, conventions/caps, billing. Purpose and the free-vs-paid fork are front-loaded, and there is no filler or restatement of the title.

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

Completeness5/5

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

With an output schema covering return values and rich annotations covering safety, the description only needs to supply conventions, caps, and cost — and it does all three. Nothing an agent needs to call this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already defines range, start, end, and include_history, making the baseline 3. The description adds the 750-returned-points cap, which the schema does not state, and reinforces the 730-day bound and the units convention. Marginal but real value beyond the schema.

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?

States a specific verb and resource: 'Return the current Argentina country-risk spread and deltas, with optional history.' That resource is distinct from every sibling (get_history, treasury_curve, get_bonds), so an agent can route on it. It stops short of naming the sibling it substitutes for, which keeps it out of 5 territory.

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

Usage Guidelines4/5

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

Gives clear context for the key decision — whether to pull history — by pairing the caps ('730 days and 750 returned points') with the cost tradeoff ('current snapshot is free; including history costs 1 read unit'). No explicit when-not or named alternative, so it isn't a 5.

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