Skip to main content
Glama

expectativas_focus

Read-onlyIdempotent

Retrieve Brazilian Central Bank Focus survey expectations for indicators such as IPCA, Selic, PIB and exchange rate, including median, mean, dispersion, current snapshot and time evolution.

Instructions

Expectativas do Relatório Focus (BCB): mediana, média e dispersão.

Sem indicador, lista os indicadores por tipo. Com indicador, traz o retrato da pesquisa mais recente (uma linha por período); com referencia ou tipo 12_meses/24_meses, traz a evolução no tempo.

Args: indicador: ex.: "IPCA", "Selic", "PIB Total", "Câmbio", "Resultado primário"; aceita apelidos (pib, dolar). tipo: "anual", "mensal", "trimestral", "12_meses", "24_meses" ou "selic" (decisões do Copom). referencia: "2027" (anual), "2026-12" (mensal), "2026-T4" (trimestral) ou "R8/2026" (selic). data: data da pesquisa (AAAA-MM-DD) para o retrato; padrão: a mais recente. inicio, ultimos, frequencia: para a evolução (padrão 12 pontos, semanal). detalhe: para "Balança comercial": "Exportações", "Importações" ou "Saldo". top5: "curto", "medio" ou "longo" para as instituições Top 5. base_calculo: 0 = últimos 30 dias (padrão); 1 = últimos 5 dias úteis. suavizada: para 12_meses e 24_meses (padrão).

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

Input Schema

NameRequiredDescriptionDefault
dataNo
tipoNoanual
top5No
inicioNo
detalheNo
ultimosNo
indicadorNo
suavizadaNo
frequenciaNosemanal
referenciaNo
base_calculoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld and idempotent, so safety is covered. The description adds real behavioral context beyond that: the tool switches between listing, snapshot and evolution modes, `data` defaults to the most recent survey, evolution defaults to 12 weekly points, and `suavizada` applies to 12_meses/24_meses. It doesn't describe what a record contains beyond 'uma linha por período'.

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?

Front-loaded with purpose, then mode behavior, then a compact Args block where every line maps to a distinct parameter. Dense but low-waste; the only soft spot is the opening 'mediana, média e dispersão' framing, which is slightly abstract before the mode rules clarify output.

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?

For an 11-parameter tool with no output schema and no schema descriptions, the definition covers modes, defaults and per-parameter formats thoroughly. Gaps are minor: no description of the returned fields beyond row-per-period, and no error behavior for an unrecognized `indicador` or mismatched `referencia` format.

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%, so the description carries the full burden, and it does: all 11 parameters are explained with accepted values, formats and aliases (`referencia` formats per `tipo`, `detalhe` values for Balança comercial, `top5` buckets, `base_calculo` 0/1 semantics, `suavizada` default). This is well beyond what the bare schema provides.

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?

Names a specific resource (Expectativas do Relatório Focus, BCB) and the statistics returned (mediana, média, dispersão), so the agent knows what data it gets. It stops short of naming sibling tools like copom or sgs_serie, so differentiation from the broader indicator family is implicit rather than stated.

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 gives explicit mode-selection rules: no `indicador` lists indicators by type, `indicador` alone returns the latest survey snapshot, and `referencia` or tipo 12_meses/24_meses returns the time series. That is strong conditional guidance; it just doesn't cover when to prefer this tool over the sibling series tools.

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