Skip to main content
Glama

get_address_by_cep

Retrieve the street, neighborhood, city, and state for an 8-digit Brazilian CEP postal code, with or without a dash, to resolve postal codes into addresses.

Instructions

Return the address (street, neighborhood, city, state) for a Brazilian CEP.

Args: cep: Postal code with 8 digits, with or without the dash (e.g. "01310-100").

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": "get_address_by_cep"
  }
}

Input Schema

NameRequiredDescriptionDefault
cepYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; 'Return' plus the listed fields reasonably signals a read-only lookup. However it does not disclose failure behavior for malformed or non-existent CEPs, rate limits, or whether an empty result versus an error is returned, which matters for a lookup an agent may call in a loop.

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

Conciseness4/5

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

The first sentence front-loads purpose and return shape, and the Args block is short and example-driven. The Args formatting is mildly redundant with the schema but carries real format information, so it earns its place.

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 read-only lookup with no output schema, listing the returned fields and the accepted input format covers nearly everything an agent needs. The remaining gap is error/empty-result semantics, which is modest but real given there is no output schema to fall back on.

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?

Schema description coverage is 0%, so the description must compensate, and it does: it specifies 8 digits, permits the dash or no dash, and gives a concrete example format. Only the absence of constraints on non-Brazilian or malformed input keeps this from a 5.

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?

States a specific verb and resource ('Return the address ... for a Brazilian CEP') and enumerates the returned fields (street, neighborhood, city, state). It is unmistakably distinct from the finance/holiday siblings, which an agent can tell apart without opening any schema.

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 description (use it when you have a CEP and need a Brazilian address), but there is no explicit when-to-use/when-not-to-use guidance and no mention of what happens with an invalid or unknown CEP.

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