Skip to main content
Glama
Sign In
GeoAgent

GeoAgent

by AbishekFRK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

geocode

Look up a place by name or airport code to get its coordinates, kind, latitude, and longitude, or an error; use these coordinates before distance or bearing calculations.

Instructions

Look up a place by name or airport code (e.g. "Bengaluru", "BLR") in the bundled dataset.

Returns the place's name, kind, lat and lon, or an error if nothing matches. It returns coordinates only, never distances: to get a distance or bearing, call distance_bearing next. Always call this first for any place name instead of using remembered coordinates.

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

Input Schema

NameRequiredDescriptionDefault
placeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does disclose the return shape (name, kind, lat, lon), the failure mode ('an error if nothing matches'), and the hard boundary that it returns coordinates only, never distances. The remaining gap is coverage: it does not say how broad or current the bundled dataset is, which matters for a fixed local dataset.

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?

Three short sentences, front-loaded with what the tool does and what it returns before the routing advice. Every sentence adds information: lookup scope, return shape plus error case, and the distance_bearing handoff.

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 one-parameter tool with no output schema, the description supplies the input semantics, the output fields, the error condition, and the sibling handoff. Nothing an agent needs in order to call it correctly is missing.

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 coverage is 0% — the single parameter is only typed as a string titled 'Place'. The description compensates by defining the accepted value space as a place name or an airport code and illustrating both with examples, which is meaningfully more than the schema alone provides.

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 ('Look up a place') plus the accepted input kinds (name or airport code) and gives concrete examples ('Bengaluru', 'BLR'). The scope is narrowed with 'in the bundled dataset', so an agent knows this is a local lookup rather than a live geocoding service.

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?

Explicitly directs 'Always call this first for any place name instead of using remembered coordinates', which forbids a plausible wrong behavior. It also names the follow-up alternative and its condition: call distance_bearing to get a distance or bearing.

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