Skip to main content
Glama

listar_municipios

Lists municipalities for a Brazilian state (UF) with their IBGE codes for tax calculations, with optional name filtering and result limits.

Instructions

Lista os municípios de uma UF com o código IBGE (usado no cálculo).

Args: sigla_uf: Sigla da UF, ex: 'RS'. busca: Parte do nome para filtrar (ignora acentos), ex: 'porto alegre'. limite: Máximo de itens (padrão 50).

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

Input Schema

NameRequiredDescriptionDefault
buscaNo
limiteNo
sigla_ufYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose real behavior: accent-insensitive filtering ('ignora acentos') and a default cap of 50 items, which is genuinely beyond the schema. It does not state read-only nature, whether results are truncated when limite is exceeded, or what fields each municipality record contains.

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?

The purpose is front-loaded in one sentence, followed by a compact Args block with one line per parameter. No filler, though the Args block could be trimmed slightly since it restates parameter names.

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 three-parameter lookup with no output schema and no annotations, the description covers inputs well and hints at the returned IBGE code, but leaves the return shape undefined (what fields per municipality, ordering, truncation behavior). Adequate but with clear gaps for an agent that must consume the results.

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 description coverage is 0%, so the description must compensate, and it largely does: sigla_uf gets a concrete example ('RS'), busca gets a sample value and a non-obvious matching rule (accent-insensitive partial match), and limite gets its default of 50. Only minor gaps remain (e.g., is busca a substring match anywhere in the name, and is the limit a hard cap with truncation?).

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?

States a specific verb and resource ('Lista os municípios de uma UF') plus the key returned attribute (código IBGE) and its downstream use ('usado no cálculo'). It is clearly distinguishable from listar_ufs by scope (municipalities within a UF), though it never names a sibling explicitly.

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?

The phrase 'usado no cálculo' implies this is a prerequisite lookup for the tax-calculation tools, which is useful context. However, it gives no explicit when-to-use/when-not guidance, no statement about whether the UF code can be obtained via listar_ufs, and no prerequisites.

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