IBGE Brasil MCP

Busca de tabelas SIDRA

ibge_sidra_tabelas

Read-onlyIdempotent

Find IBGE SIDRA table codes by searching table names or filtering by survey. Handles everyday Portuguese terms and returns a Markdown list of matching tables.

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.0): fonte, URL, período, extração 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.

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.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: it performs a live GET against the public IBGE SIDRA API, returns a Markdown table, and explains vocabulary normalization (renda→rendimento, etc.) with a notas_vocabulario note. It could add rate-limit or pagination details, but it goes beyond the 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 well-structured with clear sections (Features, Surveys, Examples, Workflow) and front-loads the core purpose. It is somewhat long, but every section earns its place by providing routing and behavioral context. A few redundant lines (e.g., listing surveys twice) could be trimmed, but it remains efficient.

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?

For a read-only list/search tool with zero required parameters, an output schema, and full schema coverage, the description is complete. It explains the workflow position, the return format, the vocabulary normalization behavior, and the alternatives. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all three parameters. The description adds examples and explains the AND/accents/case behavior for busca, but it mostly restates what the schema says. Baseline 3 is appropriate because the schema does the heavy lifting.

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 states a specific verb ('Lists and searches available SIDRA tables') and clearly distinguishes this tool from siblings by naming the SIDRA workflow and wrappers. It also enumerates features and examples, so an agent can tell it apart from ibge_sidra_metadados and ibge_sidra 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?

The description explicitly says this is step 1 of the SIDRA workflow, names the follow-up tools (ibge_sidra_metadados, ibge_sidra), and advises that wrappers (ibge_censo, ibge_indicadores, ibge_comparar, ibge_cidades) are usually easier for common data. This gives clear when-to-use and when-not-to-use guidance.

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