Skip to main content
Glama
Sign In
mcp-TesouroDireto

mcp-TesouroDireto

by msperlin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_current_rates

Read-only

Retrieve current prices and yields for all Tesouro Direto bonds as a CSV snapshot, optionally filtering by bond family or forcing a fresh download.

Instructions

Current prices and yields for all Tesouro Direto bonds.

Returns the latest available snapshot (the most recent reference date in the data) as CSV, one row per bond and maturity, ordered by maturity.

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

Input Schema

NameRequiredDescriptionDefault
asset_codesNoBond families to include (LTN, LFT, NTN-B, NTN-B Principal, NTN-F, NTN-C, RendA+, Educa+). Omit for all bonds.
force_downloadNoIgnore today's cached file and download the source again.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only and open-world traits, and the description adds real value beyond them: output format (CSV), one row per bond and maturity, ordering by maturity, and the snapshot semantics of the most recent reference date. It does not mention caching behavior despite a force_download parameter, but that is largely covered by the schema.

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?

Two short sentences, front-loaded with the purpose and followed by the shape of the result. No filler, though the trailing line break and parenthetical make the second sentence slightly less tight than it could be.

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?

With a fully documented schema, an output schema, and annotations, the description supplies the remaining context an agent needs: what the snapshot represents and how rows are organized. A note on how current data is cached would make it fully complete.

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 100%, so both asset_codes (with the full family list) and force_download are already documented in the schema. The description adds nothing about parameters beyond the phrase 'all bonds,' which just echoes the default behavior.

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 resource and scope: current prices and yields for all Tesouro Direto bonds. The contrast with historical siblings (get_bond_data, get_bond_stats) is only implied by 'latest available snapshot' rather than stated outright.

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?

Usage is implied by 'Current' and 'most recent reference date,' suggesting this is the tool for today's data rather than history. There is no explicit when-to-use or when-to-prefer-a-sibling guidance and no stated prerequisites.

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