IBGE Brasil MCP

Busca de tabelas SIDRA

ibge_sidra_tabelas

Read-onlyIdempotent

Find and filter IBGE SIDRA tables by name, survey, or code to locate the dataset needed for census, PNAD, GDP, and other Brazilian statistics queries.

Instructions

Lists and searches available SIDRA tables.

Features:

List all SIDRA tables (aggregates)
Search by table name: every word must match (AND), accents and case ignored, and everyday Portuguese is resolved to the IBGE's own wording (renda→rendimento, desemprego→desocupação, cidade→município, gênero→sexo); when that happens the response says so in notas_vocabulario
Filter by survey (Census, PNAD, GDP, etc.)
Shows code and name of each table

SIDRA contains data from various surveys:

Demographic Census
PNAD Contínua (employment, income)
National Accounts (GDP)
Industrial Survey
Agricultural Survey

Examples:

List tables: (no parameters)
Search population tables: busca="população"
Census tables: pesquisa="censo"

This is step 1 of the SIDRA workflow: find a table code → ibge_sidra_metadados (structure) → ibge_sidra (query). For common data, a wrapper is usually easier: ibge_censo, ibge_indicadores, ibge_comparar, ibge_cidades.

Behavior: read-only and idempotent — a live GET against the public IBGE SIDRA API. Returns a Markdown table.

Input Schema

TableJSON Schema

Name	Required	Description
`busca`	No	Termos para buscar no nome das tabelas/agregados (sem distinção de acento ou caixa; AND entre as palavras; a palavra de todo dia é traduzida para a do IBGE — renda→rendimento, desemprego→desocupação, cidade→município)
`limite`	No	Número máximo de resultados (padrão: 20)
`pesquisa`	No	Filtrar por código ou nome da pesquisa (ex: 'censo', 'pnad', 'pib')

Output Schema

TableJSON Schema

Name	Required	Description
`busca`	No	Termo de busca aplicado, se houver
`total`	Yes	Total de tabelas que correspondem aos critérios
`tabelas`	Yes	Lista de tabelas SIDRA retornadas
`pesquisa`	No	Filtro de pesquisa aplicado, se houver
`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)
`notas_vocabulario`	No	Quando a busca foi ampliada para a palavra que o IBGE usa (renda→rendimento), diz qual

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv5.4.0Sep 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"
+]

Changed2 schema fields changedv5.1.1Sep 17, 2026

changedInput schema / properties / busca / description

Previous value: -"Termo para buscar no nome das tabelas/agregados"New value: +"Termos para buscar no nome das tabelas/agregados (sem distinção de acento ou caixa; AND entre as palavras; a palavra de todo dia é traduzida para a do IBGE — renda→rendimento, desemprego→desocupação, cidade→município)"

addedOutput schema / properties / notas_vocabulario

Added value: +{
+  "description": "Quando a busca foi ampliada para a palavra que o IBGE usa (renda→rendimento), diz qual",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed1 schema field changedv5.0.0Sep 12, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
Changed4 schema fields changedv4.0.0Aug 29, 2026
- removedOutput schema / properties / provenance / properties / data_vintage / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / provenance / properties / data_vintage / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / provenance / properties / license / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / provenance / properties / license / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed6 schema fields changedv3.3.0Aug 17, 2026

changedInput schema / $schema

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

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / $schema

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

addedOutput schema / properties / attribution

Added value: +{
+  "description": "URLs canônicas das fontes desta resposta (lista de atribuição)",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / provenance

Added value: +{
+  "additionalProperties": false,
+  "description": "Bloco de proveniência (contrato v1.0): fonte, URL, período, extração e licença",
+  "properties": {
+    "citation": {
+      "description": "Citação pronta para uso",
+      "type": "string"
+    },
+    "data_vintage": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Período de referência do dado segundo a fonte; null se a fonte não expõe"
+    },
+    "license": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Regime legal do dado"
+    },
+    "retrieved_at": {
+      "description": "Instante real da extração no upstream (ISO-8601, horário de Brasília)",
+      "type": "string"
+    },
+    "source": {
+      "description": "Fonte oficial do dado (API do IBGE consultada)",
+      "type": "string"
+    },
+    "source_url": {
+      "description": "URL canônica que reproduz a consulta",
+      "type": "string"
+    }
+  },
+  "required": [
+    "source",
+    "source_url",
+    "data_vintage",
+    "retrieved_at",
+    "citation",
+    "license"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "tabelas",
-  "total"
-]New value: +[
+  "tabelas",
+  "total",
+  "provenance",
+  "attribution"
+]

Changed1 schema field changedv3.0.0Jun 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "busca": {
+      "description": "Termo de busca aplicado, se houver",
+      "type": "string"
+    },
+    "pesquisa": {
+      "description": "Filtro de pesquisa aplicado, se houver",
+      "type": "string"
+    },
+    "tabelas": {
+      "description": "Lista de tabelas SIDRA retornadas",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "codigo": {
+            "description": "Código da tabela/agregado SIDRA",
+            "type": "string"
+          },
+          "nome": {
+            "description": "Nome da tabela/agregado",
+            "type": "string"
+          },
+          "pesquisa": {
+            "description": "Pesquisa de origem (código - nome)",
+            "type": "string"
+          }
+        },
+        "required": [
+          "codigo",
+          "nome"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Total de tabelas que correspondem aos critérios",
+      "type": "number"
+    }
+  },
+  "required": [
+    "tabelas",
+    "total"
+  ],
+  "type": "object"
+}

First observedv1.0.0Jan 23, 2026

TDQS

A4.6/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 the safety profile is covered; the description nonetheless adds real context by stating this is a live GET against the public IBGE SIDRA API and that the response is a Markdown table. It also discloses non-obvious behavior beyond the annotations: everyday Portuguese is silently mapped to IBGE terminology, and the response flags that mapping in notas_vocabulario. It does not discuss rate limits or error behavior, so not a 5.

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 the core purpose, then structured into Features, Surveys, Examples and Workflow sections — easy to scan. The bulleted list of SIDRA surveys (Census, PNAD, GDP, Industrial, Agricultural) is largely filler that the 'pesquisa' parameter already implies, costing some tightness.

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?

An output schema exists so return values need not be explained, yet the description still notes the Markdown table format. With zero required parameters, 100% schema coverage, and explicit workflow placement and wrapper alternatives, an agent has everything needed to select and call this tool 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 description coverage is 100%, so the baseline is 3 and the schema already documents busca, limite and pesquisa including the vocabulary mapping. The description goes modestly beyond by giving worked parameter examples (busca="população", pesquisa="censo"), but does not clarify limite's default/max or AND semantics beyond what the schema states.

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 opens with a specific verb+resource ('Lists and searches available SIDRA tables') and immediately distinguishes itself from siblings by naming itself as step 1 of the SIDRA workflow, with ibge_sidra_metadados and ibge_sidra as the downstream steps. An agent can tell this apart from the wrapper tools (ibge_censo, ibge_indicadores) 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 Guidelines5/5

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

It gives explicit routing: use this first to find a table code, then ibge_sidra_metadados for structure, then ibge_sidra for the query — and adds a when-not branch ('For common data, a wrapper is usually easier: ibge_censo, ibge_indicadores, ibge_comparar, ibge_cidades'). Concrete invocation examples (no parameters, busca="população", pesquisa="censo") remove remaining ambiguity.

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