Skip to main content
Glama

divida_publica_federal

Read-onlyIdempotent

Retrieve federal public debt stock by type and instrument, plus emissions, redemptions, and interest factors, from Tesouro Nacional monthly reports by month range.

Instructions

Dívida Pública Federal (Tesouro): estoque por tipo e instrumento, e fatores de variação.

Lê o Relatório Mensal da Dívida. Anexo 2.1 (padrão): estoque no fim do mês, em R$ bilhões, desde dez/2000. Anexo 2.9: emissões, resgates e juros apropriados, em R$ milhões. Sem período, traz os 12 meses mais recentes. Não é a DBGG do BCB, que tem outro perímetro. Principais itens no catálogo (dpf_*).

Args: inicio, fim: mês (AAAA-MM). ultimos: meses recentes. linhas: filtro por texto ("lft", "dpfe", "juros"); separe com ";". anexo: "2.1" (padrão) ou "2.9". listar: só a lista de linhas do anexo.

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

Input Schema

NameRequiredDescriptionDefault
fimNo
anexoNo2.1
inicioNo
linhasNo
listarNo
ultimosNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the safety profile is covered. The description adds non-obvious behavior beyond that: differing units per annex (R$ bilhões for 2.1 versus R$ milhões for 2.9), coverage starting dez/2000, and the fallback to 12 months. It does not describe output shape or any limits on the text filter, leaving some behavioral gaps.

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?

Front-loads the resource and unit-bearing annexes in two sentences, then a compact Args block that maps one line per parameter. No filler and no restatement of the tool name.

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?

No output schema exists, and the description mostly covers returns by stating stock is broken out by type and instrument with explicit units, plus mention of dpf_* catalog items. It stops short of naming the returned columns or how `linhas` filtering affects the result set, a minor gap for a read-only reporting tool.

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

Parameters5/5

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

Schema description coverage is 0%, and the description fully compensates for all six parameters: inicio/fim as AAAA-MM, `ultimos` as recent-month count, `linhas` as a text filter with example tokens and ";" separator, `anexo` allowed values, and `listar` as list-only mode. This is meaning the schema cannot supply on its own.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: reads the Relatório Mensal da Dívida, Anexo 2.1 for end-of-month stock and Anexo 2.9 for emissions/redemptions/accrued interest. It also delimits scope against a lookalike ("Não é a DBGG do BCB, que tem outro perímetro"), so an agent can distinguish it without opening any schema.

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 operating context: default annex 2.1, default window of the 12 most recent months when no period is supplied, the choice between 2.1 and 2.9, and the use of `listar` to enumerate lines before filtering. It explicitly excludes the BCB DBGG series, but names no sibling tool as the alternative path, so guidance is clear rather than exhaustive.

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