IBGE Brasil MCP

Panorama municipal (Cidades@)

ibge_cidades

Read-onlyIdempotent

Retrieve detailed IBGE indicators for one Brazilian municipality, such as population, HDI, GDP, education, and finances, plus historical series and available surveys.

Instructions

Queries municipal indicators from IBGE (similar to Cidades@ portal).

Features:

General overview of a municipality (population, HDI, GDP, etc.)
Query specific indicators
Historical indicator data over years
List available surveys and indicators

Available indicators: populacao, area, densidade, pib_per_capita, idh, escolarizacao, mortalidade, salario_medio, receitas, despesas

Examples:

São Paulo overview: tipo="panorama", municipio="3550308"
Population history: tipo="historico", municipio="3550308", indicador="populacao"
View surveys: tipo="pesquisas"
Available indicators: tipo="indicador"

This tool is the panel for a SINGLE municipality (Cidades@). Use a different tool when:

Census themes / historical series → ibge_censo
Comparing multiple municipalities → ibge_comparar
A macro indicator time series → ibge_indicadores

Behavior: read-only and idempotent — a live GET against the public IBGE APIs (Cidades@/agregados). Returns Markdown plus a typed structuredContent payload.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`uf`	No	Código ou sigla da UF para filtrar (ex: 35 ou SP)
`tipo`	No	Tipo de consulta: panorama (resumo geral), indicador (específico), pesquisas (listar), historico	panorama
`pesquisa`	No	ID da pesquisa para filtrar indicadores
`indicador`	No	ID do indicador ou nome para busca
`municipio`	No	Código IBGE do município (7 dígitos)

Output Schema

TableJSON Schema

Name	Required	Description
`nome`	No	Nome do município/indicador
`tipo`	Yes	Tipo de consulta (panorama, indicador, pesquisas, historico)
`municipio`	No	Código IBGE do município
`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)
`indicadores`	Yes	Indicadores retornados (vazio para respostas de catálogo)

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"
+]

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: -[
-  "tipo",
-  "indicadores"
-]New value: +[
+  "tipo",
+  "indicadores",
+  "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": {
+    "indicadores": {
+      "description": "Indicadores retornados (vazio para respostas de catálogo)",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "ano": {
+            "type": "string"
+          },
+          "nome": {
+            "type": "string"
+          },
+          "valor": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "nome",
+          "valor"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "municipio": {
+      "description": "Código IBGE do município",
+      "type": "string"
+    },
+    "nome": {
+      "description": "Nome do município/indicador",
+      "type": "string"
+    },
+    "tipo": {
+      "description": "Tipo de consulta (panorama, indicador, pesquisas, historico)",
+      "type": "string"
+    }
+  },
+  "required": [
+    "tipo",
+    "indicadores"
+  ],
+  "type": "object"
+}

First observedv1.0.0Jan 23, 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 the safety profile is covered. The description still adds useful context beyond annotations: it identifies the underlying source ('live GET against the public IBGE APIs (Cidades@/agregados)') and the return shape ('Markdown plus a typed structuredContent payload'). It does not discuss rate limits or error modes, but with annotations covering behavior, this is solid.

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 with the core purpose, then cleanly sectioned into features, available indicators, runnable examples, sibling routing, and behavior. Every block is scannable and earns its place, with no redundant prose.

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 described beyond the brief note about Markdown plus structuredContent. Combined with the valid-indicator list and examples, the definition gives an agent everything needed to call a five-parameter, zero-required 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, but the description adds real value: it enumerates the valid indicator identifiers (populacao, area, densidade, pib_per_capita, etc.) that the schema does not contain, and gives concrete example parameter combinations (tipo="historico", municipio="3550308", indicador="populacao") that clarify how tipo interacts with the other fields.

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 (queries) and resource (municipal indicators), and explicitly frames the tool as the panel for a SINGLE municipality (Cidades@). The routing paragraph names the exact siblings it must not be confused with (ibge_censo, ibge_comparar, ibge_indicadores), so an agent can distinguish it without opening a 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?

Provides explicit when-to-use conditions via the feature list (overview, specific indicator, historical, list surveys) and explicit when-NOT-to-use conditions naming the correct alternatives for census themes, multi-municipality comparison, and macro time series. Nothing is left to inference.

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