Skip to main content
Glama

geoagentic

by app.geoagentic
OverviewDiscussionsAdmin

geo-wiki

Find info about notable/historic landmarks, towns, and remarkable sites near a coordinate.

USE FOR:

  • "What's near Predjama Castle?"

  • "Notable landmarks around Ljubljana center"

  • "Tell me about places near 46.05, 14.51"

  • Finding historic, cultural, or geographic summaries for an entire area at once.

  • DO NOT iterate over the results to query individual items again.

  • One call is sufficient to answer the user's broad geographic inquiry. Combine the results into a single comprehensive summary for the user immediately.

NOT FOR: directions, finding specific cafes/shops, raw geocoding.

Input Schema

NameRequiredDescriptionDefault
latYesLatitude of the search center.
lonYesLongitude of the search center.
distNoSearch radius in metres (max 10 000).
limitNoMax results (1–50).
timeoutNoHard timeout in seconds (max 60).

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.6/5.0
Behavior5/5

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

No annotations are provided, so the description carries full burden. It discloses that one call is sufficient and results should be combined into a single comprehensive summary, and warns against iterating. No destructive behavior is implied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections for purpose, use cases, and exclusions. It is slightly verbose but each sentence adds value. Front-loaded with the main purpose.

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?

Given the tool has 5 parameters with full schema coverage, no output schema, and clear usage scenarios, the description provides sufficient context. It covers behavioral expectations (combine results, no iteration) and limitations, making it complete for a tool of this complexity.

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% with descriptions for all parameters. The description does not add additional meaning beyond the schema; it only restates the coordinate parameters implicitly in examples. Baseline of 3 is appropriate as the schema does the heavy lifting.

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 finds info about notable/historic landmarks, towns, and remarkable sites near a coordinate. It uses specific verbs ('Find info') and resource ('landmarks, towns, sites'), and distinguishes from sibling tools like geo-geocode, geo-reverse, geo-route, etc.

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?

The description provides explicit 'USE FOR' examples and a 'NOT FOR' section listing exclusions (directions, finding specific cafes/shops, raw geocoding). It also advises against iterating over results and instructs to combine into a single summary.

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