Skip to main content
Glama

Parse a postal address into parts and check the postcode

address_parse
Read-only

Splits a free-text postal address into house number, street, unit, postcode, city, district, region and country, with a normalised one-line form. The postcode is checked against the rule of the country (for 18 countries); a mismatch is left out and says so. Workers AI does the split, so check the parts. geocode=1 adds coordinates from OpenStreetMap Nominatim. Related tools on this server, for a different need: crypto_address_risk when you need to check crypto addresses against OFAC digital-currency sanctions. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "address": "<address>"
    },
    "name": "address_parse"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe address as free text, up to 500 characters
countryNoISO2 code of the country when you know it, e.g. DE (optional, improves the postcode check)
geocodeNo1 to add coordinates from OpenStreetMap, default 0

Output Schema

NameRequiredDescriptionDefault
modelNo
partsNo
sourceNo
geocodeNo
checkedAtNo
normalisedNo
postcodeNoteNo
postcodeRuleCheckedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: discloses that postcodes are checked against country rules for 18 countries, that mismatches are dropped and reported, that Workers AI performs the split so results need verification, and the exact billing model ($0.002 per successful call via x402, failures free). The reliability caveat and the cost model are exactly the details annotations cannot carry.

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?

Front-loaded with the split behavior and its output parts, then layered with the postcode-check caveat and pricing in a dense but scannable run. Slightly diluted by the crypto_address_risk aside, which is the least relevant sentence for the primary task.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter tool with a full annotation set, 100% schema coverage and an output schema, the description covers everything an agent needs: what is produced, how reliable it is, what geocode adds, and what it costs. Nothing material is left to inference.

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 all three parameters are already documented, and the description largely restates them (geocode=1 adds OSM Nominatim coordinates, country refines the postcode check). The only marginal addition is naming the coordinate source, so the baseline of 3 applies.

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?

Names a specific verb and resource ("Splits a free-text postal address into...") and enumerates the exact output fields (house number, street, unit, postcode, city, district, region, country, normalised one-line form), which distinguishes it from the bare postcode and geocode siblings. An agent knows precisely what it gets back 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 Guidelines4/5

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

Gives clear context for when to use it (free-text address parsing) and explicitly routes one adjacent need elsewhere (crypto_address_risk for OFAC-sanctioned crypto addresses). However, it never explains when to prefer the closely related postcode or geocode tools instead, which are the alternatives an agent would most plausibly confuse it with; the redirect it does offer targets a distant sibling.

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