Skip to main content
Glama
Sign In
GeoAgent

GeoAgent

by AbishekFRK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

features_within

Lists cities or airports within a given radius of a latitude/longitude point, nearest first, to answer "what is within X km of..." after geocoding the location.

Instructions

List all places within radius_km of a point, nearest first. kind can be "city" or "airport".

Use for "what is within X km of ..." questions. Get the point from geocode first.

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": {
      "lat": "<lat>",
      "lon": "<lon>",
      "radius_km": "<radius_km>"
    },
    "name": "features_within"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYes
lonYes
kindNo
radius_kmYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and does provide useful details such as nearest-first ordering and the allowed kind values. However, it omits radius limits, result limits, default behavior when kind is omitted, and explicit read-only/no-side-effect context.

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?

The description is short and front-loaded, with the core operation first and the usage hint second. Every sentence contributes useful selection or invocation context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has four parameters, no schema descriptions, no annotations, and an output schema. The description covers purpose, prerequisite, ordering, and kind values, but leaves gaps around optional-kind behavior and geospatial limits that matter for correct invocation.

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 description coverage is 0%, so the description must add meaning, and it does: it identifies lat/lon as the point, clarifies radius_km as the search radius, and enumerates kind as city or airport. It still does not define coordinate format, radius bounds, or the effect of omitting kind.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: list places within radius_km of a point, nearest first. It also names the allowed kind values, but it does not explicitly distinguish this from the sibling nearest_features tool.

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 clearly states the use case for "what is within X km" questions and gives the prerequisite to obtain the point via geocode first. It does not explain when to use a different sibling instead or any exclusions.

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