Skip to main content
Glama

Mapa coroplético municipal

ibge_mapa
Read-onlyIdempotent

Generate a municipal choropleth map as SVG from official IBGE indicators and meshes for 2–50 municipalities in one state. It supports quantile/equal-interval classes and returns SVG map data.

Instructions

Generates a municipal choropleth map as SVG from audited SIDRA indicators and official IBGE municipal meshes.

Scope of this first cartographic release:

  • 2 to 50 municipalities

  • all municipalities must belong to the same state

  • indicators: populacao, populacao_censo, pib, area, densidade, alfabetizacao, domicilios

  • classification: quantiles or equal intervals

  • output: lightweight metadata plus complete SVG in structuredContent.svg

The SVG includes municipal polygons, sequential classes, legend, title, tooltips and source note. The server fetches the state municipal mesh at minimum quality and filters it to the requested municipalities.

Use a different tool when:

  • You need only geometry/download URL → ibge_malhas

  • You need non-cartographic comparison/ranking → ibge_comparar

  • You need thematic territorial composition (biomes, metropolitan regions, etc.) → ibge_malhas_tema

Behavior: read-only and idempotent. The map is a server-side derived product from official IBGE SIDRA data and official IBGE geographic meshes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "municipios": "<municipios>"
    },
    "name": "ibge_mapa"
  }
}

Input Schema

NameRequiredDescriptionDefault
tituloNo
classesNo
larguraNo
indicadorNopopulacao
municipiosYesCódigos IBGE municipais de 7 dígitos, separados por vírgula; todos na mesma UF
classificacaoNoquantis

Output Schema

NameRequiredDescriptionDefault
svgYes
bboxYes
nomeYes
fontesYes
tabelaYes
classesYes
indicadorYes
provenanceYesBloco de proveniência (contrato v1.1): fonte, URL, período, extração e licença
attributionYesURLs canônicas das fontes desta resposta (lista de atribuição)
localidadesYes
classificacaoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, but the description adds real behavioral context beyond them: hard scope limits (2–50 municipalities, single state), the server-side derivation chain (fetches state mesh at minimum quality, filters), and the output shape (metadata plus structuredContent.svg). It stops short of error behavior or fetch latency, so not a 5.

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 core action, then well-organized bullet lists for scope, output, and alternatives. Most sentences carry information, though the closing 'Behavior: read-only and idempotent' sentence largely repeats the annotation block, which is minor waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 spelled out, yet the description still usefully notes SVG contents and structuredContent.svg. Scope constraints, indicator coverage, and sibling routing cover what an agent needs; only the undocumented width/title/class-count parameters leave a small gap.

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

Parameters3/5

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

Schema coverage is only 17%, so the description must compensate. It clarifies municipios (2–50, same state) and classificacao (quantiles or equal intervals) and lists the indicator values, but leaves titulo, largura, and the classes count (2–7) undocumented in both schema and description. Partial compensation, so 3.

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 concrete verb+resource+output format: generates a municipal choropleth map as SVG from audited SIDRA indicators and official IBGE municipal meshes. It explicitly differentiates from siblings (ibge_malhas, ibge_comparar, ibge_malhas_tema), so an agent can route correctly without opening schemas.

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 'Use a different tool when' block names three sibling alternatives and the exact condition that selects each (geometry/download URL, comparison/ranking, thematic territorial composition). When-to-use and when-not-to-use are both explicit.

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