Skip to main content
Glama
Sign In
mcp-server-brasil

mcp-server-brasil

by vicgamelo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Municípios por UF (IBGE)

listar_municipios
Read-onlyIdempotent

Lists all municipalities for a given Brazilian state (UF), including each municipality's IBGE code, so you can retrieve official local identifiers for data lookup and validation.

Instructions

Lista os municípios de uma UF com o código IBGE de cada um.

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
ufYes

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

The annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds that each entry carries an IBGE code, but since an output schema exists that fact is largely redundant, and nothing is said about whether the data is static or fetched live, or about rate limits.

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?

One front-loaded sentence that states the action, the input scope, and the returned fields, with zero filler. Nothing could be removed without losing information.

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 simple read-only lookup with annotations and an output schema, this is close to sufficient: the agent knows what it gets back and that it need only pass a state code. A brief note on data source freshness or result size would make it complete.

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 would normally have to compensate, but the single parameter is a fully enumerated list of 26 state codes, leaving little ambiguity. The phrase "de uma UF" does clarify that the argument is a federal-unit code acting as a filter, but adds no format or behavior detail.

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 verb and resource ("Lista os municípios") plus the scope ("de uma UF") and even the payload ("com o código IBGE de cada um"). That is unambiguous on its own; it does not differentiate from siblings, but the siblings cover entirely different resources (CEP, CNPJ, DDD, feriados), so no confusion arises.

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 by the resource itself — an agent infers it should call this to enumerate municipalities for a given state. There is no explicit when-to-use statement, no precondition, and no mention of alternatives for state-level lookups. Adequate but with a clear gap.

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

Deploy Server

Other Tools