Skip to main content
Glama

Geocode a place name

geocode_location

Resolve a free-text place name to candidate latitude/longitude coordinates, so ambiguous locations can be identified before passing chosen coordinates to weather tools.

Instructions

Resolve a free-text place name (e.g. "Tokyo", "Springfield, Illinois") to candidate latitude/longitude coordinates. Use this first when a user names an ambiguous place, then pass the chosen coordinates to the weather 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": {
      "query": "<query>",
      "count": "<count>"
    },
    "name": "geocode_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
countYesMaximum number of candidate matches to return (1-10).
queryYesPlace name to search for, e.g. "Springfield".

Output Schema

NameRequiredDescriptionDefault
queryYes
matchesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It usefully discloses that the return is a set of *candidate* matches rather than a single definitive point, which is real behavioral information. However, it says nothing about behavior on no match, partial matches, or whether the lookup is a pure read, so there are still gaps for a zero-annotation tool.

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 sentences, each earning its place: the first defines the operation and its output, the second gives ordering and downstream routing. The purpose is front-loaded with no filler.

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?

An output schema exists and the parameters are fully documented, so the description need not detail return values. For a two-parameter read-style lookup, the definition covers what the tool does and how it fits the workflow; only edge-case behavior (no matches, multiple matches) is left unaddressed.

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 coverage is 100%, so both parameters are already documented, meaning the baseline of 3 applies. The description adds modest value by framing results as ambiguous candidates and by showing that qualified names ("Springfield, Illinois") improve disambiguation, but it does not explain the meaning or tuning of 'count' beyond the schema.

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: resolving a free-text place name to candidate latitude/longitude coordinates. The examples ("Tokyo", "Springfield, Illinois") make the granularity concrete, and the mention of the weather tools makes clear it is the geographic-resolution step rather than a data-fetching one.

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 an explicit trigger ("use this first when a user names an ambiguous place") and an explicit next action ("pass the chosen coordinates to the weather tools"), which routes the agent to the sibling tools. The only mild gap is that it does not state what to do if the user already supplies coordinates, but the sequencing instruction is otherwise complete.

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

Deploy Server

Other Tools