Skip to main content
Glama

geoagentic

by app.geoagentic
OverviewDiscussionsAdmin

eu-transit-router

EU-wide public intercity transit router. Accepts PLACE NAMES (not coordinates). Returns multi-leg itineraries via Transitous.

CRITICAL FOR AGENTS:

  • This tool handles geocoding internally. Do NOT pre-geocode or look up coordinates.

  • Do NOT call this tool multiple times with different spellings. Call it ONCE.

  • If a location isn't found, present the error message and STOP.

TEMPORAL HANDLING: This tool returns live real-time schedules only (no date parameter). If user asks for 'tomorrow' or a future date, pass it as --requested-date. The tool will add an explanatory note about schedule patterns.

EXAMPLES:

  • --from "Ljubljana, Slovenia" --to "Maribor, Slovenia"

  • --from "Podbrdo" --to "Nova Gorica" --requested-date "2026-06-05" --limit 3

  • --from "Bled" --to "Trieste, Italy" --modes "BUS WALK"

FAILURE MODES (present directly to user, do not retry):

  • LOCATION_NOT_FOUND → Check spelling

  • NO_ROUTES_FOUND → Try different modes or check locations are in Europe

  • ROUTING_FAILURE → Upstream API error, try again later

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of alternative itineraries to return. Range: 1-5.
modesNoSpace-separated transport modes. Allowed: TRANSIT WALK BUS RAIL TRAM SUBWAY FERRY BICYCLE CAR. Always include WALK with TRANSIT.TRANSIT WALK
to_placeYesDestination place name. Example: 'Nova Gorica, Slovenia'
from_placeYesOrigin place name. Example: 'Podbrdo, Slovenia' or 'Ljubljana'
requested_dateNoUser's requested date in YYYY-MM-DD format (optional). Used only to generate a note about real-time vs. future schedules.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "to_place",
-  "from_place"
-]New value: +[
+  "from_place",
+  "to_place"
+]
  2. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "from_place",
-  "to_place"
-]New value: +[
+  "to_place",
+  "from_place"
+]
  3. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "to_place",
-  "from_place"
-]New value: +[
+  "from_place",
+  "to_place"
+]
  4. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "from_place",
-  "to_place"
-]New value: +[
+  "to_place",
+  "from_place"
+]
  5. Changed9 schema fields changed
    • removedInput schema / properties / end_lat
      Removed value: -{
-  "description": "Destination latitude, WGS84 decimal. Example: 46.5622",
-  "type": "number"
-}
    • removedInput schema / properties / end_lon
      Removed value: -{
-  "description": "Destination longitude, WGS84 decimal. Example: 15.6554",
-  "type": "number"
-}
    • addedInput schema / properties / from_place
      Added value: +{
+  "description": "Origin place name. Example: 'Podbrdo, Slovenia' or 'Ljubljana'",
+  "type": "string"
+}
    • changedInput schema / properties / modes / description
      Previous value: -"Space-separated transport modes. Allowed: TRANSIT WALK BUS RAIL TRAM SUBWAY FERRY BICYCLE CAR. Always include WALK with TRANSIT. Example: 'TRANSIT WALK'"New value: +"Space-separated transport modes. Allowed: TRANSIT WALK BUS RAIL TRAM SUBWAY FERRY BICYCLE CAR. Always include WALK with TRANSIT."
    • addedInput schema / properties / requested_date
      Added value: +{
+  "description": "User's requested date in YYYY-MM-DD format (optional). Used only to generate a note about real-time vs. future schedules.",
+  "type": "string"
+}
    • removedInput schema / properties / start_lat
      Removed value: -{
-  "description": "Origin latitude, WGS84 decimal. Example: 46.0569",
-  "type": "number"
-}
    • removedInput schema / properties / start_lon
      Removed value: -{
-  "description": "Origin longitude, WGS84 decimal. Example: 14.5058",
-  "type": "number"
-}
    • addedInput schema / properties / to_place
      Added value: +{
+  "description": "Destination place name. Example: 'Nova Gorica, Slovenia'",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "start_lon",
-  "end_lon",
-  "end_lat",
-  "start_lat"
-]New value: +[
+  "from_place",
+  "to_place"
+]
  6. Added

TDQS

A4.6/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses geocoding internally, live real-time schedules, and failure modes. Could be more explicit about output format, but covers key behavioral traits.

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?

Well-structured with sections for critical instructions, temporal handling, examples, and failure modes. Slightly verbose but every section adds value for an agent.

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?

Comprehensive given no output schema and 5 parameters. Covers purpose, usage, parameters, failure modes, and temporal handling. Examples illustrate all parameter combinations.

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 100%, so baseline is 3. Description adds functional context: place names (not coordinates), requested-date usage, modes allowed with WALK requirement, and limit range. Elevates above baseline.

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 is an 'EU-wide public intercity transit router' accepting place names and returning multi-leg itineraries. It distinguishes from siblings like geo-route by focusing on public transit and handling geocoding internally.

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 when-to-use instructions: do not pre-geocode, call once, present errors, and handle temporal requests with requested-date. Failure modes and examples provide clear guidance on usage vs 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