Skip to main content
Glama

bcb_serie_valores

Read-onlyIdempotent

Retrieve historical values of a Brazilian Central Bank time series by SGS code, with optional date range filtering. Returns series metadata and data points.

Instructions

Consulta o histórico de valores de UMA série temporal do BCB pelo código SGS, opcionalmente limitado por um intervalo de datas (dataInicial/dataFinal). Quando usar: para obter a série histórica completa ou uma janela de datas específica. Quando NÃO usar: para apenas os pontos mais recentes use bcb_serie_ultimos; para a variação percentual use bcb_variacao; para comparar várias séries use bcb_comparar; se não souber o código, descubra-o antes com bcb_buscar_serie ou bcb_series_populares. Retorna: objeto serie (codigo, nome, categoria, periodicidade), totalRegistros, periodoInicial, periodoFinal e dados (array de {data, valor}); quando não há dados, totalRegistros = 0 e uma observacao explicativa. Comportamento: consome a API pública SGS do Banco Central do Brasil — sem autenticação, chave de API ou cadastro, e sem limite de requisições divulgado (uso é best-effort). Em falha transitória ou timeout a chamada é repetida automaticamente (até 3 tentativas, backoff exponencial); persistindo o erro, retorna isError: true com mensagem em português (HTTP 404 = série inexistente ou sem dados no período solicitado). O resultado vem como JSON tanto em texto quanto em structuredContent (conforme o outputSchema); datas no formato dd/MM/yyyy e valores numéricos (ponto decimal).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codigoYesCódigo da série no SGS/BCB (ex: 433 para IPCA mensal, 11 para Selic)
dataInicialNoData inicial no formato yyyy-MM-dd ou dd/MM/yyyy (opcional)
dataFinalNoData final no formato yyyy-MM-dd ou dd/MM/yyyy (opcional)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
serieYes
totalRegistrosYesQuantidade de observações retornadas
periodoInicialNoData da primeira observação
periodoFinalNoData da última observação
dadosYesObservações históricas
observacaoNoMensagem informativa (ex.: quando não há dados)
Behavior5/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint as safe/read-only. Description adds extensive behavioral details: no authentication, best-effort rate limit, retry logic (3 attempts, exponential backoff), error handling returns isError with Portuguese messages, date and number formatting. No contradiction with annotations.

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?

Every sentence is informative, front-loaded with main purpose, then usage, return structure, and behavior. No wasted words, despite length it is concise for the content.

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 output schema exists, description still covers return object structure, edge cases (no data), retry/error behavior, and authentication/rate limits. Very comprehensive for a 3-parameter tool with output schema.

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% with descriptions, baseline 3. Description adds value by explaining optional date parameters, giving example codes (433, 11), and stating return format details related to parameters. Slight improvement over baseline.

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?

The description clearly states it consults historical values of a BCB time series by SGS code, optionally with date range. It uses specific verbs and resources, and distinguishes from sibling tools by listing when to use alternatives.

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

Usage Guidelines5/5

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

Explicitly provides both 'Quando usar' and 'Quando NÃO usar' sections with specific alternative tool names (bcb_serie_ultimos, bcb_variacao, bcb_comparar, bcb_buscar_serie, bcb_series_populares).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SidneyBissoli/bcb-br-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server