Skip to main content
Glama
radar-cnpj-mcp

radar-cnpj-mcp

by wendersoon

Buscar município

buscar_municipio
Read-only

Search imported Brazilian municipalities by partial name, ignoring accents, with optional state (UF) filtering to return matching records.

Instructions

Encontra municípios pelo nome (busca parcial, sem diferenciar acentos) entre as UFs importadas.

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": "buscar_municipio"
  }
}

Input Schema

NameRequiredDescriptionDefault
ufNo
nomeYes
limiteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior beyond them: matching is partial (not exact) and accent-insensitive, and the search domain is restricted to already-imported UFs, which affects both query construction and empty results. It stops short of describing result ordering or return contents.

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?

A single front-loaded sentence with no filler; the matching semantics and scope appear immediately. It is efficient, though the brevity comes at the cost of the missing parameter and result-format detail noted elsewhere.

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

Completeness2/5

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

For a 3-parameter search tool with no output schema and no parameter descriptions, the definition leaves two parameters undocumented and says nothing about what a result contains or how many come back. Sufficient to guess intent, insufficient to call it correctly for anything but the simplest name-only query.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 full burden, yet only 'nome' is explained (partial, accent-insensitive). The optional 'uf' filter and 'limite' (default 20, max 100) are never mentioned, and the unexplained enum value 'EX' is left entirely to the agent's guesswork.

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 (Encontra/busca) and resource (municípios) and adds two scope qualifiers: partial string matching and accent-insensitivity. It is clearly distinguishable from buscar_empresas and buscar_cnae by resource, though it never names a sibling or the complementary perfil_municipio tool.

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 implied rather than stated: an agent can infer this is the lookup tool for municipality names, and the phrase 'entre as UFs importadas' hints that data must be imported first. There is no explicit guidance on when to prefer this over perfil_municipio, nor any statement of what to do when no match is found.

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