brasil-mcp-essentials

Official

Overview Schema Source Related Servers Discussions Admin

lookup_endereco_cep

Search for Brazilian postal codes (CEP) by providing state, city, and street address. Supports partial street matching and caches results for 30 days.

Instructions

Busca lista de CEPs por endereço (UF + cidade + logradouro) via ViaCEP (online). Aceita match parcial no logradouro. 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": {
      "uf": "<uf>",
      "cidade": "<cidade>",
      "logradouro": "<logradouro>"
    },
    "name": "lookup_endereco_cep"
  }
}

Input Schema

Name	Required	Description	Default
`uf`	Yes
`cidade`	Yes
`logradouro`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jul 30, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations provided, so description carries burden. It discloses use of external service (ViaCEP), partial matching on logradouro, and 30-day caching. Does not cover rate limits or error handling, but adequate for a lookup tool.

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?

Single sentence, front-loaded with verb and resource, no redundant words. Highly efficient.

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

Completeness5/5

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

Output schema exists, so return values are covered. Tool is simple; description covers all necessary aspects: inputs, external dependency, caching, partial matching.

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 coverage is 0% (no descriptions). Description mentions parameters but does not specify format (e.g., uf abbreviation or full name, cidade format). Partial match hint is helpful but insufficient.

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?

Description clearly states it searches for CEPs by address using ViaCEP, specifies inputs (UF, cidade, logradouro), and mentions caching and partial matching. Differentiates from sibling lookup_cep which does the reverse.

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

Usage Guidelines4/5

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

Context is clear: use when you need to find CEPs from an address. Does not explicitly state when not to use or mention alternatives, but the purpose is unambiguous.

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