Skip to main content
Glama
location-risk-mcp

location-risk-mcp

Standardise address

standardise_address
Read-onlyIdempotent

Converts free-text addresses into a standardized, geocoded location with a location_id for property risk screening, returning match status, gaps, and US risk enrichment.

Instructions

Turn a free-text address into one standardised, geocoded location with a location_id.

country is an ISO 3166 alpha-3 code (USA, IND, GBR, ...). Returns status 'matched' (use location.location_id next), 'ambiguous' (ask the user to choose from candidates) or 'no_match'. Missing components are listed in gaps. Risk enrichment covers US addresses only; elsewhere the risk blocks come back as gaps.

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

Input Schema

NameRequiredDescriptionDefault
addressYes
countryNoUSA

Output Schema

NameRequiredDescriptionDefault
gapsNo
inputYes
statusYes
locationNoSet only when status is 'matched'
warningsNoInput the provider corrected (e.g. a different ZIP): confirm with the applicant
candidatesNoSet when status is 'ambiguous': ask the user which one, do not pick
provenanceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, so the safety profile is covered. The description adds substantive behaviour beyond that: the three status outcomes, that missing components surface in 'gaps', and the important limitation that risk enrichment applies to US addresses only with other regions returning gaps. Only return-format/pagination-style detail is absent, and an output schema exists.

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?

Two short paragraphs, front-loaded with the core transformation, followed by the country format and then outcome handling. No redundant sentences; each line carries new information.

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 two-parameter, low-complexity tool with an output schema present, this covers everything an agent needs: input format, country encoding, outcome branching, follow-up action, gap reporting, and the US-only risk caveat.

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 carries the burden and does so for 'country': an ISO 3166 alpha-3 code with examples (USA, IND, GBR). The 'address' parameter is only implied by 'free-text address', so coverage is good but not complete.

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?

States a specific verb and resource: converts free-text address into a standardised, geocoded location with a location_id. This is clearly distinct from enrich_location or summarise_risk_context, but the description never explicitly names or contrasts those siblings.

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?

Provides clear post-call routing ('use location.location_id next', 'ask the user to choose from candidates') for the matched/ambiguous/no_match outcomes, which is genuinely useful. It does not say when to reach for this tool versus enrich_location or summarise_risk_context, so alternative selection is left implicit.

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