Skip to main content
Glama

Geocode Address or Landmark

alterlab_geocode

Resolve an informal address, place name or landmark description (including distance hints like 'a school 67 m away, a university 272 m away') to coordinate candidates. Each candidate has name, address, lat, lng, a 0-1 confidence that rises when sources agree, and the source and source_url it came from. Pass near (lat/lng), city or country to bias results. Cost: priced like one search query; no charge when nothing is found.

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": {
      "query": "<query>"
    },
    "name": "alterlab_geocode"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity or area name used to bias the search.
nearNoBias point: candidates closer to it rank higher.
queryYesInformal address or landmark description.
countryNoISO 3166-1 alpha-2 country code.
max_resultsNoMaximum candidates returned. Default: 5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing candidate shape (name, address, lat, lng, confidence, source, source_url) and non-obvious cost behavior: 'priced like one search query; no charge when nothing is found.' That billing nuance is real operational context no annotation conveys. It stops short of noting result ordering beyond confidence or failure/timeout behavior.

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?

Three tight sentences, front-loaded with the action and immediately followed by the return shape and then the biasing/cost notes. Dense but every clause carries information; only the parenthetical distance-hint example feels slightly bulky.

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?

With no output schema, the description correctly compensates by enumerating candidate fields and explaining confidence semantics and source attribution. Cost and empty-result behavior are covered. Minor gaps: no mention of result ordering rules, request limits, or what happens when the query is ambiguous and zero candidates are returned.

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 documents every parameter including bounds and the max_results default. The description merely restates that near/city/country 'bias results' without adding format, precedence (what happens if both near and city are passed), or conflict-handling detail, so baseline 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?

States a specific verb and resource: 'Resolve an informal address, place name or landmark description ... to coordinate candidates.' It also scopes what input kinds are accepted (distance hints quoted verbatim), so an agent can tell this is a geocoding resolver rather than a general search or extract tool.

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?

Gives one line of usage context ('Pass near (lat/lng), city or country to bias results') and a cost note, which implies when the tool is appropriate. However it never says when NOT to use it, what to do for structured addresses vs. landmarks, or how it relates to any alternative resolution path, so guidance is implied rather than explicit.

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.