Skip to main content
Glama
Sign In

Transit Land

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Departures At Stop

departures_at_stop
Read-onlyIdempotent

Upcoming departures from a stop. stop_id is the Transitland onestop_id (e.g. "s-9q8yvz3w7-stopname").

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "stop_id": "s-9q8yvz3w7-marketst",
      "end_time": "09:30:00",
      "start_time": "08:00:00",
      "service_date": "2024-01-15"
    },
    "name": "departures_at_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
stop_idYesTransitland onestop_id for the stop
end_timeNoHH:MM:SS
start_timeNoHH:MM:SS
service_dateNoYYYY-MM-DD (default today)

Output Schema

NameRequiredDescriptionDefault
departuresNoList of upcoming departures

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "end_time": "09:30:00",
+    "service_date": "2024-01-15",
+    "start_time": "08:00:00",
+    "stop_id": "s-9q8yvz3w7-marketst"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Upcoming departures from a stop",
+  "properties": {
+    "departures": {
+      "description": "List of upcoming departures",
+      "items": {
+        "properties": {
+          "arrival_time": {
+            "description": "Arrival time HH:MM:SS",
+            "type": "string"
+          },
+          "departure_time": {
+            "description": "Departure time HH:MM:SS",
+            "type": "string"
+          },
+          "route": {
+            "description": "Route details",
+            "type": "object"
+          },
+          "stop_sequence": {
+            "description": "Stop sequence in trip",
+            "type": "number"
+          },
+          "trip": {
+            "description": "Trip details",
+            "properties": {
+              "id": {
+                "type": "string"
+              },
+              "route_id": {
+                "type": "string"
+              },
+              "trip_id": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds context by explaining the result is 'upcoming departures' and specifying the stop_id format. No contradictions, and it supplements annotations with concrete formatting details.

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 a single concise sentence that immediately states the purpose, followed by an inline example for the key parameter. Every word is functional; no fluff. Front-loaded with the core action.

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 presence of an output schema and comprehensive annotations, the description is complete for a simple query tool. It covers the main purpose, key parameter format, and default behavior. No missing critical details.

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%, meaning all 4 parameters are described in the input schema. The description adds value by providing an explicit example of a valid stop_id and hinting at default behavior for service_date ('default today'). This goes beyond the schema's format descriptions.

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's purpose: 'Upcoming departures from a stop.' It uses a specific verb ('Upcoming departures') and resource ('stop'), differentiating it from sibling tools like search_stops which find stops, not departures.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains that stop_id must be a Transitland onestop_id and provides an example, implying the requirement. However, it does not explicitly state when to use this tool vs alternatives, nor does it provide negative usage guidance. The sibling list includes search_stops for finding stop IDs, but no direct mention.

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

All Transit Land 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