Skip to main content
Glama

grid402_cep

Read-onlyIdempotent

Brazilian CEP postal lookup: street, neighborhood, city, state and IBGE code (0.0050 USDC / 1 credit).

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": {
      "code": "<code>"
    },
    "name": "grid402_cep"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes8-digit Brazilian CEP postal code (e.g. 01310100).
payment_tx_hashNoOptional txHash on Base Mainnet, Session Pass token (pass_g402_...), EIP-3009 base64 payload, or demo for Sandbox.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / code / description
      Previous value: -"CEP, ex: 01310100"New value: +"8-digit Brazilian CEP postal code (e.g. 01310100)."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the per-call cost (0.0050 USDC / 1 credit), which tells an agent this is a paid metered operation, and the shape of the returned address data.

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?

A single front-loaded sentence that states the resource, the return fields and the price with zero filler. Nothing needs trimming and nothing important is buried.

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-required-parameter read-only lookup, the definition covers purpose, output fields and cost, and the schema covers both parameters fully. Minor gaps remain: no statement on invalid-CEP behavior, error responses, or how the payment parameter interacts with the call (e.g. whether it is required for production vs sandbox).

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?

Schema description coverage is 100%, with both 'code' and 'payment_tx_hash' documented in-schema (including the 8-digit format and payment mechanisms). The description adds no parameter-level meaning, so the baseline of 3 applies.

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 uses a specific verb ('postal lookup') and names the exact resource ('Brazilian CEP'), then enumerates the returned fields (street, neighborhood, city, state, IBGE code). This clearly separates it from siblings like grid402_cnpj (company registry) or grid402_lei, though it never names an alternative explicitly.

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: an agent can infer 'use this when you need address data from a Brazilian postal code,' but there is no explicit when-to-use/when-not-to-use statement or routing to alternative tools. No prerequisites or exclusions are stated.

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.

Resources