Skip to main content
Glama
Sign In
grid402-mcp

grid402-mcp

by oliveiratc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

grid402_cep

Looks up Brazilian postal address data from an 8-digit CEP, returning street, neighborhood, municipality, state, and official IBGE code.

Instructions

Consulta a base pública de endereçamento postal brasileiro retornando logradouro, bairro, município, UF e código IBGE oficial.

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
codeYesCódigo de CEP brasileiro com 8 dígitos numéricos (ex: "01310100" para Av. Paulista).
payment_tx_hashNoHash opcional de transação na Base Mainnet com 0.0005 USDC.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a read-only public lookup, but says nothing about the paid access implied by the payment_tx_hash parameter (0.0005 USDC on Base Mainnet), nor about rate limits, failure behavior for unknown CEPs, or caching — all material for an agent deciding whether and how to call it.

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?

A single front-loaded sentence with zero filler that leads with the action and resource. It is efficient, though the brevity leaves behavioral questions unanswered rather than being trimmed of value.

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?

For a two-parameter lookup with no output schema, listing the returned fields is genuinely helpful and the input side is fully covered by the schema. However, the absence of any payment/cost or error-handling context leaves the definition only minimally complete given the paywalled parameter in the schema.

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%, so the schema already explains the 8-digit CEP format and the optional payment hash. The description adds only the returned-field list, which does not deepen parameter meaning beyond what the schema states; baseline 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 ('Consulta') plus a precise resource ('base pública de endereçamento postal brasileiro') and enumerates the returned fields (logradouro, bairro, município, UF, código IBGE). This clearly separates it from siblings such as grid402_cnpj or grid402_forex, 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no mention of preconditions, and no routing to any sibling tool. An agent must infer that this is the CEP lookup versus, say, grid402_verify purely from the resource noun.

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