Skip to main content
Glama
SidneyBissoli

IBGE Brasil MCP

by SidneyBissoli
OverviewSchemaRelated ServersScoreDiscussions
TypeScript

ibge_malhas_tema

Read-onlyIdempotent

Fetch thematic geographic meshes (biomes, legal Amazon, etc.) from IBGE in GeoJSON, TopoJSON, or SVG format.

Instructions

Gets thematic geographic meshes from IBGE.

Available themes:

  • biomas: Brazilian biomes (Amazon, Cerrado, Atlantic Forest, Caatinga, Pampa, Pantanal)

  • amazonia_legal: Legal Amazon area

  • semiarido: Semi-arid region

  • costeiro: Coastal zone

  • fronteira: Border strip

  • metropolitana: Metropolitan regions

  • ride: Integrated Development Regions

Biome codes:

  • 1: Amazon

  • 2: Cerrado

  • 3: Atlantic Forest

  • 4: Caatinga

  • 5: Pampa

  • 6: Pantanal

Examples:

  • All biomes: tema="biomas"

  • Amazon biome: tema="biomas", codigo="1"

  • Legal Amazon: tema="amazonia_legal"

  • Metropolitan regions: tema="metropolitana"

  • With municipalities: tema="biomas", resolucao="5"

  • List themes: tema="listar"

Use a different tool when:

  • Administrative meshes (Brazil/region/state/municipality outlines) → ibge_malhas

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
temaYesTema da malha: - biomas: Biomas brasileiros (Amazônia, Cerrado, etc.) - amazonia_legal: Área da Amazônia Legal - semiarido: Região do semiárido - costeiro: Zona costeira - fronteira: Faixa de fronteira - metropolitana: Regiões metropolitanas - ride: Regiões Integradas de Desenvolvimento - listar: Lista temas disponíveis
codigoNoCódigo específico do tema (ex: código do bioma, da região metropolitana)
formatoNoFormato de saídageojson
resolucaoNo0 = Apenas contorno, 5 = Com municípios0
qualidadeNoQualidade do traçado: 1=mínima, 4=máxima4

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
temaYesTema da malha solicitada (ou 'listar')
codigoNoCódigo específico do tema, quando informado
formatoNoFormato de saída (geojson, topojson, svg)
resolucaoNoResolução da malha (0 = contorno, 5 = com municípios)
temasNoLista de temas disponíveis (somente no modo 'listar')

Tool Definition Quality

A5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds value by confirming it's a live GET against the IBGE API, that it returns requested formats (GeoJSON, TopoJSON, SVG), and is read-only/idempotent, enhancing transparency beyond annotations.

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-organized into sections (available themes, biome codes, examples, alternative tool usage) without redundancy. Every sentence adds value, making it efficient and easy to parse.

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 the tool has 5 parameters (with enums) and an output schema exists, the description completely covers all aspects: purpose, themes, codes, formats, resolution, quality, and behavioral characteristics. No gaps remain.

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

Parameters5/5

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

Schema coverage is 100% with each parameter described. The description adds significant value by providing concrete examples, biome codes, and usage patterns (e.g., tema='biomas', codigo='1') that enrich understanding beyond 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?

The description clearly states it gets thematic geographic meshes from IBGE, listing available themes and providing examples. It explicitly distinguishes from sibling tool 'ibge_malhas' which handles administrative meshes.

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 states when to use this tool vs. 'ibge_malhas' for administrative meshes. It provides extensive context with available themes, codes, and examples, leaving no ambiguity.

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