CensoSenso MCP

Dados de países

ibge_paises

Read-onlyIdempotent

Query official IBGE country data to list all countries, view details, search by name, or filter by continent. Includes area, languages, currency, and location.

Instructions

Queries international country data via IBGE.

Features:

List all countries (following UN M49 methodology)
Country details (area, languages, currency, location)
Search countries by name
Filter by region/continent

Available regions: americas, europa, africa, asia, oceania

Country codes: Use ISO-ALPHA-2 (e.g., BR, US, AR, PT, JP)

Examples:

List all: tipo="listar"
Brazil details: tipo="detalhes", pais="BR"
Search: tipo="buscar", busca="Argentina"
Americas countries: tipo="listar", regiao="americas"
Available indicators: tipo="indicadores"

Behavior: read-only and idempotent — queries the public IBGE Países API when data is requested and returns Markdown plus typed structuredContent with provenance.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`pais`	No	Código ISO-ALPHA-2 do país (ex: BR, US, AR) ou código M49
`tipo`	No	Tipo de consulta: listar (todos), detalhes (de um país), indicadores, buscar	listar
`busca`	No	Termo de busca para filtrar países pelo nome
`regiao`	No	Filtrar por região/continente: americas, europa, africa, asia, oceania
`indicadores`	No	IDs dos indicadores separados por \| (ex: 77819\|77820), usados apenas com tipo=detalhes

Output Schema

TableJSON Schema

Name	Required	Description
`pais`	No	Detalhes de um país específico (modo detalhes)
`tipo`	Yes	Modo de consulta que originou este resultado
`busca`	No	Termo de busca aplicado, se houver
`total`	No	Total de países encontrados (modos listar/buscar)
`paises`	No	Lista de países (modos listar/buscar). Limitada aos 50 primeiros na exibição
`regiao`	No	Filtro de região/continente 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)
`indicadores`	No	Indicadores disponíveis para consulta de países (modo indicadores)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Oct 5, 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/idempotentHint/openWorldHint, so the safety profile is covered. The description adds value beyond that by naming the backing source (public IBGE Países API) and the return shape (Markdown plus typed structuredContent with provenance).

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 purpose, then cleanly sectioned into Features, regions, codes, examples, and behavior. It is somewhat long and repeats region values already present in the schema, but no sentence is wasted and the structure is easy to scan.

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?

With an output schema present, the description needn't detail returns, and it still sketches the response format. Combined with annotations covering safety and a fully-documented 5-parameter schema, nothing an agent needs 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 is 3, but the description goes further by pairing parameters in worked examples (e.g., tipo="detalhes" with pais="BR", tipo="listar" with regiao="americas"), clarifying valid combinations. The region and ISO-ALPHA-2 details largely restate 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 international country data via IBGE") and enumerates the four query modes. The 'países/countries' resource is clearly distinct from the state, municipality, and locality siblings, so an agent can route without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The Examples block shows concrete invocation patterns for every mode (listar, detalhes, buscar, region filter, indicadores), giving clear context for how to use the tool. It stops short of stating when-not-to-use or naming a sibling alternative, so it lacks explicit exclusions.

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