Skip to main content
Glama

Latam Validate

Brasil Cep

brasil_cep
Read-onlyIdempotent

Look up a Brazilian CEP (postal code) and return the address: street, neighborhood, city, and state, with coordinates when available. Example: CEP 01310-100 -> Avenida Paulista, Bela Vista, São Paulo, SP.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cep": "01310-100"
    },
    "name": "brasil_cep"
  }
}

Input Schema

NameRequiredDescriptionDefault
cepYesThe 8-digit CEP, e.g. "01310-100" or "01310100".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "cep": "01310-100"
      +  },
      +  {
      +    "cep": "01310100"
      +  }
      +]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description still adds real value by disclosing the shape of the result and that coordinates are only sometimes present ("when available"), which is the key behavioral caveat an agent needs.

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 sentences, front-loaded with the action and return shape, followed by a compact concrete example. Nothing is wasted and nothing is missing that belongs here.

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?

With no output schema, the description correctly shouldered the burden of describing return values and does so field by field, including the conditional coordinates. Only minor gaps remain, such as behavior on an invalid or unfound CEP.

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?

Only one parameter and schema description coverage is 100%, with the schema itself showing both accepted formats and an examples array. The description's worked example (01310-100 -> Avenida Paulista...) illustrates output rather than adding parameter meaning, so baseline 3 is right.

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?

Specific verb plus resource: "Look up a Brazilian CEP (postal code) and return the address", and it enumerates the returned fields (street, neighborhood, city, state, coordinates). No sibling tool does CEP lookup, so there is no ambiguity to resolve.

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 by the narrow purpose — an agent knows to call it when it has a CEP and needs an address — but the description states no conditions, prerequisites, or when-not-to-use, and does not point at any alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.