Skip to main content
Glama
Sign In

Listing Location Toolkit

by io.github.Nero-Engine
OverviewDiscussionsAdmin

Find an address

locate_address
Read-onlyIdempotent

Turns an address or UK postcode into latitude and longitude, with the matched address and the source (US Census Geocoder, postcodes.io or Nominatim). Use it to check the pin before the other tools.

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

Input Schema

NameRequiredDescriptionDefault
addressYesStreet address with town and ZIP or postcode, e.g. "7090 State Highway 80, Cooperstown, NY 13326" or "Ambleside LA22 9BB". Not needed when lat and lon are given.
countryNoOptional hint for the address lookup.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so safety and side-effect profile are covered. The description adds meaningful context by naming the external geocoding sources (US Census Geocoder, postcodes.io, Nominatim), which signals network dependence and source attribution. It does not discuss failure modes or ambiguity resolution.

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 tightly written sentences with no wasted words. The core function and the returned values are front-loaded, followed by the usage instruction.

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 geocoding tool with no output schema, the description explains what comes back: latitude, longitude, matched address, and source. It is nearly complete, though it omits behavior when an address is ambiguous or not found, and does not address the schema's mention of lat/lon inputs.

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 address and country parameters are already documented in the schema, including examples and the US/UK enum. The description adds little beyond saying 'address or UK postcode' and does not clarify the country hint or the schema note about lat/lon being given. Baseline 3 applies when the schema carries the parameter detail.

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?

The description states a specific verb and resource — turning an address or UK postcode into latitude and longitude — and names the returned fields (matched address and source). An agent can distinguish this geocoding step from the sibling analysis tools without opening the 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?

It gives clear sequencing guidance: 'Use it to check the pin before the other tools,' which tells the agent this is a prerequisite step for the location-based siblings. It stops short of naming specific alternatives or stating when not to use it, but the ordering context is explicit.

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

All Listing Location Toolkit toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources