Skip to main content
Glama
Sign In
mcp-TesouroDireto

mcp-TesouroDireto

by msperlin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_yield_curve

Read-only

Retrieves the current Brazilian yield curve from ANBIMA (ETTJ) as CSV, including real, nominal, and implicit-inflation rates by maturity, with an option to bypass the 30-minute cache.

Instructions

Current Brazilian yield curve from ANBIMA (ETTJ).

Returns CSV with `n_biz_days`, `type` (real_return, nominal_return or
implicit_inflation), `value` in percent per year, the derived `ref_date`
(maturity) and ANBIMA's `current_date`.

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

Input Schema

NameRequiredDescriptionDefault
forceNoIgnore the 30-minute cache and fetch ANBIMA again.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the external-fetch safety profile is covered. The description adds useful context about the CSV columns and the ANBIMA source, but does not disclose the 30-minute caching behavior (deferred to the parameter schema) or freshness/latency expectations.

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?

Two tight sentences, front-loaded with the source and resource, followed by the return shape. No filler.

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?

An output schema exists, yet the description helpfully enumerates the key columns, and the source is identified. What is missing is the temporal coverage of 'current' (e.g., latest snapshot only) and any link to how this differs from current-rates siblings.

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?

The single parameter has full schema coverage, and the schema already explains 'force' as bypassing the 30-minute cache. The description adds nothing about the parameter, so baseline 3 applies for high coverage.

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 (current Brazilian yield curve, ANBIMA ETTJ) and the exact returned fields, so the agent knows precisely what it fetches. It does not distinguish itself from sibling get_current_rates or get_bond_data, so it falls 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?

There is no explicit when-to-use guidance and no mention of alternatives such as get_current_rates, which appears closely related. The only implied guidance is the word 'current', leaving the agent to infer the scope.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools