Skip to main content
Glama
SidneyBissoli

IBGE Brasil MCP

by SidneyBissoli
OverviewSchemaRelated ServersScoreDiscussions
TypeScript

ibge_malhas

Read-onlyIdempotent

Retrieve geographic mesh maps of Brazil in GeoJSON, TopoJSON, or SVG format. Supports all administrative levels from country to municipalities with configurable resolution and quality.

Instructions

Gets geographic meshes (maps) from IBGE in GeoJSON, TopoJSON, or SVG format.

Features:

  • Meshes for Brazil, regions, states, municipalities

  • Different resolution levels (internal divisions)

  • Different quality levels

  • Formats: GeoJSON (data), TopoJSON (compact), SVG (image)

Locality types:

  • "BR" or "1" = Entire Brazil

  • State abbreviation (e.g., "SP", "RJ")

  • State code (e.g., "35" for SP)

  • Municipality code (7 digits)

Resolution (internal divisions):

  • 0 = Outline only

  • 2 = States

  • 5 = Municipalities

Examples:

  • Brazil with states: localidade="BR", resolucao="2"

  • São Paulo with municipalities: localidade="SP", resolucao="5"

  • SVG format: localidade="BR", formato="svg"

Use a different tool when:

  • Thematic meshes (biomes, Legal Amazon, semi-arid, metropolitan regions) → ibge_malhas_tema

Behavior: read-only and idempotent — a live GET against the public IBGE Malhas API. Returns the mesh in the requested format (GeoJSON, TopoJSON, or SVG).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
localidadeYesCódigo IBGE ou sigla da localidade (ex: 'BR', 'SP', '35', '3550308')
tipoNoTipo de divisão territorial
formatoNoFormato de saída (padrão: geojson)geojson
resolucaoNoResolução/divisões internas: 0 = Sem divisões internas 1 = Macrorregiões (apenas para BR) 2 = Unidades da Federação 3 = Mesorregiões 4 = Microrregiões 5 = Municípios0
qualidadeNoQualidade do traçado: 1=mínima, 2=baixa, 3=intermediária, 4=máxima4
intrarregiaoNoCódigo de região para filtrar (apenas quando localidade=BR)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
localidadeYesCódigo IBGE ou sigla da localidade consultada
formatoYesFormato de saída solicitado (geojson, topojson ou svg)
resolucaoNoResolução/divisões internas solicitada
qualidadeNoQualidade do traçado solicitada
tipoNoTipo de divisão territorial, quando informado
intrarregiaoNoCódigo de região usado para filtrar (apenas quando localidade=BR)
urlNoURL para download da malha completa

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds 'Behavior: read-only and idempotent — a live GET against the public IBGE Malhas API. Returns the mesh in the requested format.', which aligns and adds context without contradiction.

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?

The description is well-structured with sections (overview, features, locality types, resolution, examples, alternatives). Every sentence is meaningful, no redundancy, and front-loaded with the core purpose.

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?

Given 6 parameters (1 required, 4 enums, output schema exists), the description covers usage, parameter details, output formats, and an alternative tool. No gaps for this complexity.

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 baseline is 3. The description adds value by explaining locality types with examples (e.g., 'BR', 'SP', '35'), resolution meanings (0-5), format defaults, and quality levels, going beyond the schema's enum descriptions.

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 'Gets geographic meshes (maps) from IBGE in GeoJSON, TopoJSON, or SVG format.' with a specific verb and resource, and distinguishes from sibling 'ibge_malhas_tema' by explicitly mentioning thematic meshes.

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 description provides clear context with examples and a 'Use a different tool when' section that names 'ibge_malhas_tema' for thematic meshes. It lacks explicit when-not-to-use beyond that, but is sufficient.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SidneyBissoli/ibge-br-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server