brasil-mcp-essentials

Official

Overview Schema Source Related Servers Discussions Admin

lookup_ibge_municipio

Retrieve the IBGE code for any Brazilian municipality by its name, with optional state filter and accent-insensitive search.

Instructions

Consulta código IBGE de município brasileiro por nome (acento-insensível). UF opcional. Cacheado 30 dias.

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": {
      "nome": "<nome>"
    },
    "name": "lookup_ibge_municipio"
  }
}

Input Schema

Name	Required	Description	Default
`uf`	No
`nome`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jul 30, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. Only mentions caching and accent-insensitivity. Lacks disclosure of what happens if no match or multiple matches, any rate limits, or side effects.

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?

Extremely concise: one sentence with three key points. No filler, front-loaded with primary action. Every word adds value.

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?

Covers essential aspects: purpose, accent-insensitivity, optional parameter, caching. Output schema exists so return format is not needed. Minor gap: does not mention possible multiple results for ambiguous names.

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 0%, so description must compensate. Adds meaning: nome is municipality name (accent-insensitive), uf is optional state. However, does not specify format for uf (e.g., 'SP' vs 'São Paulo') or that it returns a list.

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?

Clearly states the tool consults IBGE codes of Brazilian municipalities by name, with accent-insensitive matching. Distinct from sibling tools that focus on validation and parsing of documents and other lookups.

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?

Provides basic usage context (accent-insensitive, optional state, caching) but does not specify when to use vs alternatives, which are all different, but also lacks prerequisites or when-not guidance.

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