Skip to main content
Glama

geocode_location

Read-onlyIdempotent

Resolve a place name to coordinates, country, timezone, and population, then use the returned latitude/longitude for weather lookups.

Instructions

Resolve a place name to coordinates, country, timezone and population.

Call this first when you only have a place name, then pass the returned latitude/longitude into any weather tool.

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

Input Schema

NameRequiredDescriptionDefault
nameYesPlace name to search for, e.g. 'Berlin', 'Austin, TX', 'Kyoto'.
max_resultsNoMaximum matches to return (1-10).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety and external-lookup profile is covered. The description adds the useful chaining behavior and names the data returned, but does not discuss what happens when a name is ambiguous and multiple matches come back.

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 sentences with zero filler; the primary purpose comes first and the usage instruction follows. Nothing needs trimming.

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?

The tool is simple, has a rich annotation set and an output schema, so return-value explanation is not mandatory and the description covers purpose plus sequencing. The one gap is disambiguation behavior when multiple places share a name, which the parameter max_results implies is possible.

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%, with both 'name' and 'max_results' fully documented including examples and the 1-10 range. The description adds no parameter-level detail such as how to phrase names or why to raise max_results, so the 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?

The description opens with a specific verb and resource ('Resolve a place name to coordinates') and enumerates the returned fields (country, timezone, population), which distinguishes it cleanly from the coordinate-consuming weather siblings. An agent can tell what this tool does 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 Guidelines5/5

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

It gives an explicit selection rule: 'Call this first when you only have a place name,' and states the follow-up action of passing latitude/longitude into any weather tool. That ordering guidance directly addresses the ambiguity an agent faces when holding only a place name.

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