Skip to main content
Glama

Moradas — Portuguese addresses & postal codes

suggest_address

Autocomplete a Portuguese address or postal code. Pass free text (street, optionally locality and door number, e.g. 'av liberdade lisboa 196') or a postal code (e.g. '1000-098'). Returns suggestions with street, localidade (postal locality), concelho, distrito and cp7. When cp7 is null the street spans several postal codes: call resolve_postal_code with art_id and the door number. The beginning of a municipality or large locality name ('lisb', 'carcav') returns that place itself first (art_id 0). A suggestion found after correcting a typo or the street type in q ('rua agusta' or 'avenida augusta lisboa' → Rua Augusta) carries corrected: true.

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": {
      "q": "<q>"
    },
    "name": "suggest_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesStreet text (with optional door number) or a 4–7 digit postal code
countNoMax suggestions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it enumerates the returned fields (street, localidade, concelho, distrito, cp7), explains the null-cp7 edge case, the art_id 0 self-result, and the corrected: true flag. It stops short of stating safety/auth expectations or whether results are ranked or truncated, leaving a small gap for a read-only-looking autocomplete.

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?

Front-loads the core action in the first sentence, then adds edge-case behavior in order of likely encounter (returned fields, null cp7, partial-name matches, typo correction). Every sentence supplies information the agent could not get from the schema.

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?

No output schema exists, so the description correctly takes on return-value explanation by naming all five returned fields and the meaning of a null cp7. It is nearly complete for a two-parameter lookup tool, with only ranking/ordering behavior of suggestions left unstated.

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 coverage is 100%, so baseline is 3, but the description adds genuine meaning: it clarifies that q accepts free street text with optional locality and door number or a postal code, and shows accepted shapes for both. The count parameter is left entirely to the schema, which is acceptable given its clear inline description.

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 (autocomplete a Portuguese address or postal code) and immediately distinguishes the two input modes with concrete examples ('av liberdade lisboa 196' vs '1000-098'). It also routes to the sibling resolve_postal_code, so an agent can tell it apart from the other address tools without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives explicit conditions for the follow-up call: when cp7 is null, call resolve_postal_code with art_id and the door number. It also explains what happens with partial municipality names and how typo corrections surface, which tells the agent how to interpret rather than just when to call.

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