Skip to main content
Glama

ibge_localidades

Read-onlyIdempotent

Retrieve official IBGE state and municipality codes for territorial divisions, enabling reliable cross-referencing with SIDRA and other Brazilian data sources. Filter municipalities by UF or name.

Instructions

Divisão territorial do IBGE com os códigos oficiais (úteis para cruzar com o SIDRA e outras fontes).

nivel é 'estados' ou 'municipios'. Para municípios, informe a uf (sigla) ou um trecho do nome em consulta; sem nenhum dos dois, a lista seria o país inteiro e é recusada.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ibge_localidades"
  }
}

Input Schema

NameRequiredDescriptionDefault
ufNo
nivelNoestados
limiteNo
consultaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that — an unqualified municipios query is rejected — but says nothing about result volume, the role of 'limite' (default 50), or what the returned records look like.

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?

Two tight sentences, with the resource and the cross-reference value front-loaded before the parameter rules. The refusal clause is worth its space, though the parenthetical about SIDRA could be folded more cleanly and the opening lacks an explicit action verb.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter, open-world lookup with no output schema and no annotations explaining the data shape, the description covers the query-selection logic well but leaves 'limite' and the returned record structure (code + name pairs) unexplained. An agent can call it, but cannot predict truncation or output format.

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 description coverage is 0%, so the description carries the burden and does explain a lot: the only two valid 'nivel' values, that 'uf' takes a state abbreviation, and that 'consulta' matches a name fragment. However, 'limite' is never mentioned, so one of four parameters remains undocumented in both schema and description; baseline-plus rather than fully compensating.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource — IBGE territorial division with official codes — and states its purpose of cross-referencing with SIDRA and other sources, which lets an agent distinguish it from the SIDRA and series tools. The retrieval verb (list/fetch) is only implied by 'Divisão territorial ... com os códigos', so it is clear but slightly short of a full verb+resource statement.

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?

It gives an explicit conditional rule: for 'municipios' you must supply 'uf' (sigla) or a name fragment in 'consulta', and otherwise the request would cover the whole country and is refused. That is real when-to-use guidance, but it does not compare this tool against any sibling as an alternative.

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