Skip to main content
Glama

Septa

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Septa Rail Arrivals

septa_rail_arrivals
Read-onlyIdempotent

Philadelphia SEPTA Regional Rail departures board for a station — the next trains leaving, grouped Northbound/Southbound with train number, line, destination, scheduled vs estimated departure time, live status ("On Time" or minutes late), and track. Station names are matched forgivingly ("30th street", "ardmore", "suburban" all work). Example: septa_rail_arrivals({ station: "Suburban Station", results: 8 })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsNoDepartures to return per direction (default 8, max 30)
stationYesRegional Rail station name, e.g. "Suburban Station", "Gray 30th Street" (accepts "30th Street"), "Temple University", "Ardmore", "Airport Terminal B". Partial names are fuzzy-matched to the official station list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "station": "Suburban Station"
+  },
+  {
+    "results": 5,
+    "station": "30th Street"
+  }
+]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint false. The description adds meaningful behavioral details beyond annotations: it explains the grouping (Northbound/Southbound), the fields returned (train number, line, destination, scheduled/estimated times, live status, track), and the forgiving station name matching. It does not contradict annotations.

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 three sentences: a clear statement of purpose, a list of returned fields, and an example call. Every sentence is informative and necessary. No fluff or repetition.

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's simplicity (2 parameters, no output schema), the description fully covers input (station, results with defaults and max), output (all relevant departure fields including live status), and behavior (fuzzy matching, grouping, example). It is self-contained and does not rely on external docs.

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. The description adds value by providing an example call with both parameters ('station' and 'results') and clarifying that station names are fuzzy-matched. This enhances understanding beyond the schema's field descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it returns a 'Philadelphia SEPTA Regional Rail departures board for a station' with specific details (grouped Northbound/Southbound, train number, line, destination, times, status, track). It distinguishes itself from sibling tools by focusing on departures from a station, but does not explicitly contrast with similar tools like septa_next_to_arrive or septa_train_view. The slight mismatch between title 'arrivals' and description 'departures board' causes minor confusion.

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

Usage Guidelines2/5

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

The description does not provide guidance on when to use this tool versus alternatives such as septa_next_to_arrive, septa_bus_positions, or septa_train_view. It implies usage for rail station departures but offers no exclusions or comparative context, leaving the agent without clear selection criteria.

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

All Septa 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