IBGE Brasil MCP

by io.github.SidneyBissoli

Overview Discussions Admin

Calendário de divulgações

ibge_calendario

Read-onlyIdempotent

Queries IBGE release and collection calendar.

Features:

List upcoming survey releases
Filter by product (IPCA, PNAD, GDP, etc.)
Filter by period
Distinguish releases from field collections

Event types:

Release: Publication of survey results
Collection: Field research period

Examples:

Upcoming releases: (no parameters)
IPCA releases: produto="IPCA"
2024 calendar: de="01/01/2024", ate="31/12/2024"
Field collections: tipo="coleta"

Use a different tool when:

Already-published news and releases → ibge_noticias

Behavior: read-only and idempotent — a live GET against the public IBGE Calendário API. Returns a Markdown list.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`de`	No	Data inicial no formato DD/MM/AAAA (ex: '01/01/2024')
`ate`	No	Data final no formato DD/MM/AAAA (ex: '31/12/2024')
`tipo`	No	Tipo de evento: 'divulgacao' (publicações), 'coleta' (pesquisas de campo), ou 'todos'	divulgacao
`pagina`	No	Número da página (padrão: 1)
`produto`	No	Filtrar por produto/pesquisa (ex: 'IPCA', 'PNAD', 'PIB')
`quantidade`	No	Quantidade de resultados por página (padrão: 20)

Output Schema

TableJSON Schema

Name	Required	Description
`total`	Yes	Total de eventos disponíveis para os critérios
`pagina`	No	Página atual retornada
`eventos`	Yes	Lista de eventos do calendário (divulgações/coletas)
`produto`	No	Filtro de produto aplicado, quando informado
`provenance`	Yes	Bloco de proveniência (contrato v1.1): fonte, URL, período, extração, diagnóstico de origem e licença
`attribution`	Yes	URLs canônicas das fontes desta resposta (lista de atribuição)
`totalPaginas`	No	Total de páginas disponíveis

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 27, 2026

changedOutput schema / properties / provenance / description

Previous value: -"Bloco de proveniência (contrato v1.0): fonte, URL, período, extração e licença"New value: +"Bloco de proveniência (contrato v1.1): fonte, URL, período, extração, diagnóstico de origem e licença"

addedOutput schema / properties / provenance / properties / retrieval

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "anomalies": {
+          "description": "Anomalias superadas até o sucesso, somadas por classe, em ordem fixa; [] se nenhuma",
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "count": {
+                "description": "Ocorrências desta classe na chamada",
+                "maximum": 9007199254740991,
+                "minimum": 1,
+                "type": "integer"
+              },
+              "kind": {
+                "description": "Classe da anomalia (vocabulário fechado do contrato)",
+                "enum": [
+                  "timeout",
+                  "network",
+                  "http_4xx",
+                  "http_5xx",
+                  "rate_limited",
+                  "malformed_body"
+                ],
+                "type": "string"
+              }
+            },
+            "required": [
+              "kind",
+              "count"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "attempts": {
+          "description": "Tentativas somadas, incluindo as repetidas (>= requests)",
+          "maximum": 9007199254740991,
+          "minimum": 1,
+          "type": "integer"
+        },
+        "requests": {
+          "description": "Idas distintas à origem que compõem esta resposta (fatias, páginas)",
+          "maximum": 9007199254740991,
+          "minimum": 1,
+          "type": "integer"
+        },
+        "unstable": {
+          "description": "true se houve repetição (attempts > requests) ou alguma anomalia",
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "requests",
+        "attempts",
+        "anomalies",
+        "unstable"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Diagnóstico de origem desta chamada (contrato v1.1): idas à API do IBGE, tentativas somadas e anomalias contornadas; unstable=true quando houve anomalia. null quando nada foi medido (resposta servida só do cache)"
+}

changedOutput schema / properties / provenance / required

Previous value: -[
-  "source",
-  "source_url",
-  "data_vintage",
-  "retrieved_at",
-  "citation",
-  "license"
-]New value: +[
+  "source",
+  "source_url",
+  "data_vintage",
+  "retrieved_at",
+  "retrieval",
+  "citation",
+  "license"
+]

Changed1 schema field changedSep 11, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedSep 6, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds value beyond them by naming the underlying live GET to the public Calendário API and the return format (Markdown list). Minor gap: pagination behavior via pagina/quantidade is not characterized.

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-loaded one-line purpose followed by Features, Event types, Examples, and routing sections. Every section carries distinct, non-redundant information and the examples are compact.

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 an output schema exists, return values needn't be detailed, and safety is covered by annotations. The description still rounds out domain concepts (Release vs Collection event types) needed to interpret the results correctly.

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%, so the baseline is 3 and the schema already documents all six parameters. The description's examples tie parameter names to concrete values (produto="IPCA", de/ate date range, tipo="coleta"), which adds useful usage semantics beyond the schema.

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 (queries the IBGE release/collection calendar) and enumerates what it covers. It explicitly distinguishes itself from the sibling ibge_noticias, so an agent can route correctly without opening schemas.

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?

Provides explicit when-to-use context plus a 'Use a different tool when' section routing already-published news to ibge_noticias. Concrete examples (no params for upcoming, produto="IPCA", date range, tipo="coleta") map conditions to calls.

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

All IBGE Brasil MCP 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.