mcp-brasilapi

by silasrm

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

cep__buscar

Looks up the address corresponding to a Brazilian CEP (8-digit postal code, with or without hyphen).

Instructions

Busca o endereço correspondente a um CEP (8 dígitos, 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": "cep__buscar"
  }
}

Input Schema

Name	Required	Description	Default
`cep`	Yes	CEP a ser consultado, ex.: "01310930" ou "01310-930".

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 16, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description should disclose behavioral traits (e.g., error handling, response characteristics). It only states the basic function and input format, lacking details such as required permissions, rate limits, or behavior for invalid 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?

The description is extremely concise: a single sentence with no unnecessary words. It is front-loaded with the core verb and resource.

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

Completeness3/5

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

Given that an output schema exists, the description does not need to explain return values. However, it lacks context about error handling, rate limits, or how this tool compares to the sibling 'cep__buscar_v2'. Adequate for a simple lookup but incomplete for more complex scenarios.

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?

The schema coverage is 100% and the description's mention of '8 dígitos, com ou sem hífen' repeats the schema's parameter description. No additional semantic value is provided beyond the schema.

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 clearly states the tool's function: looking up an address by CEP. It specifies the input format (8 digits, with or without hyphen). However, it does not differentiate from the sibling 'cep__buscar_v2', which is a gap.

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

Usage Guidelines2/5

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

No usage guidelines are provided. The description does not mention when to use this tool versus alternatives like 'cep__buscar_v2', nor any prerequisites or special conditions.

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