Skip to main content
Glama
Sign In
mcp-server-brasil

mcp-server-brasil

by vicgamelo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Consultar CEP

consultar_cep
Read-onlyIdempotent

Retrieve the Brazilian address and coordinates for a CEP code, including street, neighborhood, city, and state, to resolve postal code location data.

Instructions

Endereço (logradouro, bairro, cidade, UF e coordenadas quando houver) de um CEP.

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

NameRequiredDescriptionDefault
cepYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered without description help. The one piece of added behavior is the parenthetical 'quando houver' for coordinates, signalling fields may be absent. Missing are error behavior for invalid CEPs and any lookup/rate constraints, which matter for an open-world external lookup.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very short with no wasted words, but it is a bare sentence fragment that lists output fields instead of front-loading the action and required input. Brevity here is under-specification rather than efficiency.

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 simple one-parameter lookup, an output schema exists so return values need not be described — yet the description spends its only clause on exactly that. The essential missing piece is input format and usage context, leaving the definition incomplete despite the tool's low complexity.

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% with a single required 'cep' string, so the description carries the burden of explaining the parameter, yet it says nothing about format (digits only vs. hyphenated), length, or validation. The agent is left to guess the expected input shape.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun phrase naming the returned data ('endereço ... de um CEP') rather than stating an action, so the verb 'consultar' comes only from the name and title. It does convey the resource and the fields returned, which lets an agent distinguish it from consultar_cnpj or consultar_ddd, but the purpose is described obliquely.

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?

There is no indication of when to use this tool versus the sibling lookup tools, nor any precondition such as the CEP needing to be a valid 8-digit code. The agent must infer everything about invocation context from the name alone.

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

Deploy Server

Other Tools