mcp-brasil

Consultar CEP

consultar_cep

Read-onlyIdempotent

Look up a Brazilian CEP postal code to retrieve street, neighborhood, city, state, and coordinates when available. Accepts codes with or without a hyphen.

Instructions

Busca o endereço de um CEP brasileiro (rua, bairro, cidade, UF e, quando houver, coordenadas). Aceita com ou sem hífen.

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": {
      "cep": "<cep>"
    },
    "name": "consultar_cep"
  }
}

Input Schema

Name	Required	Description	Default
`cep`	Yes	CEP com 8 dígitos, ex.: 01310-100

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and idempotentHint=true, so the safety profile needs no restating. The description adds real value beyond that by naming the fields returned and flagging that coordinates are only present "quando houver", which tells the agent the response shape is variable. It stops short of describing failure behavior for malformed or unknown CEPs.

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?

Two short sentences, zero filler. The purpose and returned fields come first, and the input-format tolerance is appended as a secondary but useful detail.

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 one-parameter lookup with no output schema, the description covers the essentials: what is queried, what comes back, optional fields, and input format. Only edge-case behavior (invalid CEP, not-found response) is left unstated, which is a minor omission at this complexity.

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?

With a single parameter at 100% schema coverage, the baseline is 3, but "Aceita com ou sem hífen" adds formatting meaning the schema does not convey on its own — the schema example only shows the hyphenated form, which could mislead an agent into normalizing input unnecessarily.

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?

"Busca o endereço de um CEP brasileiro" pairs a specific verb with a specific resource and enumerates the returned fields (rua, bairro, cidade, UF, coordenadas). The tool name and resource domain make it distinguishable from siblings like consultar_cnpj or consultar_isbn, though the description itself never contrasts with them.

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: the description says what is looked up, so an agent can infer it applies to postal-code address resolution, but there is no explicit when-to-use framing, no statement about invalid or nonexistent CEPs, and no reference to alternatives. Adequate but with clear gaps.

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

Deploy Server