Skip to main content
Glama

geoagentic

by app.geoagentic

geo-geocode

Convert a place name or address into coordinates (lat/lon).

USE FOR:

  • "Where is Izola bus station?"

  • Resolving a place name before calling geo-route, geo-osm, geo-isochrone or other tools

NOT FOR: reverse lookup (coordinates → address) → use geo-reverse instead.

EXAMPLE: User: "Geocode Izola bus station" → --query "Izola bus station, Slovenia"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesAddress or place name to look up. Be specific — include city/country when possible.
timeoutNoHard timeout in seconds (max 60).

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided. The description is straightforward but lacks details on data source, rate limits, error handling, or whether the operation is idempotent. It does not expand beyond the basic function.

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 extremely concise and well-structured: a single sentence for purpose, followed by bullet-point usage guidelines and an example. Every sentence is useful and no unnecessary text.

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?

Given the simplicity of the tool (2 parameters, no output schema), the description is adequate but does not specify the exact response format or potential error messages, which would be helpful for an AI agent to interpret results.

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 both parameters well-described. The description adds marginal value by advising specificity (include city/country) and providing an example, but does not significantly enhance understanding beyond the schema.

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 action: 'Convert a place name or address into coordinates (lat/lon)'. It distinguishes itself from the sibling tool 'geo-reverse' which handles reverse lookups.

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 explicitly provides 'USE FOR' and 'NOT FOR' sections, guiding the agent to use this tool for forward geocoding and directing reverse geocoding to 'geo-reverse'. It also suggests using this tool before calling other geo tools.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation4/5

Most tools have clearly distinct purposes (geocoding vs routing vs POI search). However, the multiple Slovenian cadastral tools (simple, deep, wfs-expert) overlap in functionality, potentially confusing an agent on which to use for a given task.

Naming Consistency3/5

Tools within subgroups like 'geo-*' follow a consistent verb_noun pattern, and 'slovenia-*' tools use a noun_adjective pattern. However, across the whole set there is no unified naming convention, mixing prefixes like 'eu-', 'events-', 'hikes-', and 'hostel-'.

Tool Count4/5

With 16 tools, the server is slightly above the ideal range (3-15) but still well-scoped. Each tool addresses a distinct geographic need, although the breadth across many domains (transit, cadastre, weather, hostels) feels a bit broad.

Completeness4/5

The tool set covers core geographic operations (geocoding, routing, POI, isochrones, reverse geocoding) plus specialized Slovenian data and travel amenities. Minor gaps exist, such as lack of general worldwide POI beyond OSM or event discovery beyond Luma, but overall it is comprehensive for its domain.

Resources