Skip to main content
Glama

Listar municípios de uma UF

listar_municipios
Read-onlyIdempotent

List all municipalities in a Brazilian state with their IBGE codes, and optionally filter results by a name fragment while ignoring accents.

Instructions

Lista os municípios de um estado com o código IBGE de cada um. Aceita filtro por nome.

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": {
      "uf": "<uf>"
    },
    "name": "listar_municipios"
  }
}

Input Schema

NameRequiredDescriptionDefault
ufYesSigla do estado, ex.: MG
buscaNoTrecho do nome para filtrar (opcional, ignora acentos)

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 useful context beyond them by stating the response shape (one entry per municipality, each with an IBGE code), but says nothing about ordering, result volume, or unmatched-filter behavior.

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?

Two short sentences, no filler, and the core purpose plus return content are front-loaded before the optional filter mention. Every clause earns its place.

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?

For a two-parameter read tool with a fully documented schema and safety annotations, the description is nearly sufficient, and it compensates for the absent output schema by naming the IBGE code in the results. Only minor operational details (ordering, full-list vs filtered behavior) are missing.

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 100%: the 'uf' enum with the 'Sigla do estado, ex.: MG' description and the 'busca' accent-insensitivity note are already fully documented in the schema. The description only restates that a name filter exists, adding no syntax or matching detail beyond it, so the baseline 3 applies.

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 states a specific verb and resource ('Lista os municípios de um estado') and adds that each result carries its IBGE code, so the agent knows exactly what comes back. It does not need to distinguish itself from any sibling, since the catalog has no other municipality-listing tool, but it also does no explicit sibling positioning.

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

Usage Guidelines3/5

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

Usage is only implied: 'Aceita filtro por nome' tells the agent a filter exists but gives no guidance on when to use it versus fetching the full list, and no prerequisites or exclusions are stated. With no close alternative in the catalog, this gap is minor, but the guidance remains implicit rather than explicit.

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