Tesouro em Foco

indicator_history

Read-onlyIdempotent

Returns the full published history of a Brazilian reference series, so you can put macro context next to a bond's own rate history without leaving this server. Every rate is a decimal-fraction string, the same convention as every other tool here.

Available indicator values:

selic-target — the meta Selic set by the Copom, from the official Banco Central rate history. Annual (unit: 'annual-decimal-fraction', '0.1425' = 14.25% a.a.), so it compares with price_history_series directly.
ipca-monthly — the IPCA measured and published by the IBGE (read from Banco Central SGS series 433), every month since January 1980. Monthly (unit: 'monthly-decimal-fraction', '0.0007' = 0.07% a.m.).

ALWAYS read unit before comparing series or charting them together: an IPCA month is not an annual rate, and treating '0.0044' as 0.44% a.a. instead of 0.44% a.m. is off by more than a factor of ten. To annualize a month, compound it; to get a 12-month accumulated IPCA, compound the twelve monthly readings — do not add them.

For selic-target this is EVERY decision since the regime began in March 1999, including the meetings that held the rate (outcome: 'hold', changeBps: 0). Read outcome to tell them apart: up, down, hold, or start for the single opening entry. Count only up/down when the user asks how many times the rate actually moved.

Two selic-target fields are easy to misread. meetingNumber is NOT unique: until 2003 a meeting could set a bias ('alta'/'baixa') authorizing the Banco Central president to move the target before the next meeting, alone, and those decisions carry monocratic: true under the authorizing meeting's number — effectiveDate is the key. And effectiveRate is the Selic actually realized over the period, a different quantity from the target in rate; it is null while a period is still in force.

For ipca-monthly, referenceMonth is the month the index MEASURES, not the month it was released — the IPCA of a month comes out around the 10th of the next one, so the most recent entry is normally the previous month — or the one before it, in the first days of a month, while the release is still pending. These are realized readings only; this server holds no IPCA forecast, and the projections that go into pricing an IPCA+ bond are a different thing, not exposed here. Readings before July 1994 are from the hyperinflation era and are genuinely that large (82.39% in March 1990).

Neither series by itself sets the rate or price of any Treasury bond, and a move in the same window is not evidence that one caused the other. These are factual series, not a forecast, a market interpretation, or a recommendation.

Returns { series, unit, source: { id, publisher }, items }. For selic-target, items is [{ decisionDate, effectiveDate, rate, previousRate, changeBps, outcome, meetingNumber, extraordinary, monocratic, bias, effectiveRate }] ascending by effectiveDate. For ipca-monthly, items is [{ referenceMonth, rate }] ascending by referenceMonth, one entry per month with no gaps.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`indicator`	Yes	Which reference series to return. `selic-target` is the Selic target rate set by the Copom (Banco Central), annual. `ipca-monthly` is the IPCA published by the IBGE, monthly — the realized index, not the projection used in pricing.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 26, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed2 schema fields changedAug 23, 2026

changedInput schema / properties / indicator / description

Previous value: -"Which reference series to return. `selic-target` is the Selic target rate set by the Copom (Banco Central)."New value: +"Which reference series to return. `selic-target` is the Selic target rate set by the Copom (Banco Central), annual. `ipca-monthly` is the IPCA published by the IBGE, monthly — the realized index, not the projection used in pricing."

changedInput schema / properties / indicator / enum

Previous value: -[
-  "selic-target"
-]New value: +[
+  "selic-target",
+  "ipca-monthly"
+]

AddedJul 27, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description goes well beyond the annotations, disclosing decimal-fraction string convention, unit differences, outcome semantics (`hold`, `up`, `down`, `start`), non-unique `meetingNumber`, `effectiveRate` null behavior, `referenceMonth` timing, hyperinflation-era magnitude, and explicitly states these are factual series, not forecasts or recommendations. No contradiction with the read-only/idempotent annotations.

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 long but front-loaded with purpose and each paragraph earns its place by addressing specific misinterpretation risks. The structure flows from purpose to values to warnings to field semantics to return shape. While dense, it is not padded; the length is justified by the number of pitfalls it prevents.

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?

Given two distinct series with different units and historical quirks, the description covers all material aspects an agent needs: output shape, field semantics, sorting order, no-gap guarantee, release timing, and the tool's non-causal nature. It is complete enough to use correctly without additional lookups.

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?

Although the schema already describes the `indicator` enum with 100% coverage, the description enriches each value with concrete examples (0.1425 = 14.25% a.a., 0.0007 = 0.07% a.m.), unit conventions, and interpretation warnings (`treating '0.0044' as 0.44% a.a. instead of 0.44% a.m. is off by more than a factor of ten`). This adds meaning beyond the schema's basic descriptions.

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?

Describes a specific action ('Returns the full published history of a Brazilian reference series'), names the resource and its two variants, and explicitly connects to a use case (macro context next to bond history) and names the sibling `price_history_series` as the comparable tool. This distinguishes it from the other tools.

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?

The description frames when to use the tool ('put macro context next to a bond's own rate history without leaving this server') and references `price_history_series` as the directly comparable series. It gives clear context but does not explicitly list when not to use sibling tools; the guidance is implicit rather than exclusionary.

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

All Tesouro em Foco tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?