IBGE Brasil MCP

Panorama municipal (Cidades@)

ibge_cidades

Read-onlyIdempotent

Query municipal indicators like population, HDI, and GDP for a single Brazilian city using its IBGE code. Retrieve overviews, historical data, 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.0): fonte, URL, período, extração 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.

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

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered — the description's restatement adds little there. It does add genuinely new context: a live GET against public IBGE APIs and a return format ('Markdown plus a typed structuredContent payload'). No rate-limit or auth caveats are mentioned, but for a public read-only API this is minor.

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 purpose, then features, indicator list, examples, and routing — a logical, skimmable structure. It is somewhat long and the features list partially overlaps the examples, but each block carries usable information and no sentence is purely filler.

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 5-parameter read-only tool with full schema coverage and an output schema, the description supplies everything an agent needs: what it does, the indicator vocabulary, the routing alternatives, and the return shape. Nothing required to invoke it correctly is missing.

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 of 3 applies, but the description adds real value by enumerating the available indicators (populacao, area, pib_per_capita, idh, etc.) and showing parameter combinations per tipo. It goes beyond the schema's enum glosses without fully specifying each parameter's syntax.

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 municipal indicators from IBGE') and explicitly scopes the tool to a SINGLE municipality (Cidades@ panel). It names the exact sibling tools it is not (ibge_censo, ibge_comparar, ibge_indicadores), so an agent can disambiguate 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?

Provides explicit routing rules: 'Use a different tool when: Census themes → ibge_censo; Comparing multiple municipalities → ibge_comparar; macro indicator time series → ibge_indicadores.' It also gives worked examples mapping each 'tipo' value to a concrete scenario, leaving nothing to inference.

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