Skip to main content
Glama

geoagentic

by app.geoagentic
OverviewDiscussionsAdmin

geo-reverse

Convert coordinates (lat/lon) into a street address.

USE FOR:

  • "What's at 45.5, 13.6?"

  • Turning raw coordinates into a human-readable location

NOT FOR: place name → coordinates → use geo-geocode instead.

EXAMPLE: User: "What address is at 46.05, 14.51?" → --lat 46.05 --lon 14.51

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYesLatitude to reverse-geocode.
lonYesLongitude to reverse-geocode.
timeoutNoHard timeout in seconds (max 60).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "lon",
-  "lat"
-]New value: +[
+  "lat",
+  "lon"
+]
  2. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "lat",
-  "lon"
-]New value: +[
+  "lon",
+  "lat"
+]
  3. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "lon",
-  "lat"
-]New value: +[
+  "lat",
+  "lon"
+]
  4. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "lat",
-  "lon"
-]New value: +[
+  "lon",
+  "lat"
+]
  5. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "lon",
-  "lat"
-]New value: +[
+  "lat",
+  "lon"
+]
  6. Added

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description lacks behavioral details like return format, error handling, or rate limits, which are needed for full transparency.

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 concise, well-structured with headings, and front-loads the key purpose and usage guidance.

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?

Lacks mention of output format or error handling; could be more complete for a tool with no output schema.

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%, and the description adds minimal value beyond the schema, only showing an example usage for lat and lon without discussing the timeout parameter.

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 clearly states the tool converts coordinates to a street address with specific verb and resource, and distinguishes from sibling tool geo-geocode.

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?

Explicit 'USE FOR' and 'NOT FOR' sections with an example provide clear guidance on when to use this tool versus alternatives.

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

All geoagentic toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources