Skip to main content
Glama

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 })

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": {
      "station": "Suburban Station"
    },
    "name": "septa_rail_arrivals"
  }
}

Input 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 read-only, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds genuinely new behavior: results are grouped Northbound/Southbound, each train carries live status text and track, and station names are matched forgivingly. Not stated: pagination limits beyond `results`, or what happens for an unknown or non–Regional Rail station.

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?

One dense front-loaded sentence stating what it is and what comes back, followed by a short matching note and a single example call. Nothing is repeated and nothing extraneous; the caller knows the tool and its output shape within the first clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description properly carries the return-value burden by listing the fields and the direction grouping, and both parameters are covered. The remaining gaps (error behavior on unmatched stations, whether `results` can be 0) are minor for a read-only lookup tool.

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 description coverage is 100%, so both `station` (fuzzy match, examples) and `results` (default 8, max 30) are already documented in the schema. The description's fuzzy-match examples and its per-direction framing of `results` restate rather than extend that, so the baseline 3 applies.

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?

Opens with a specific verb+resource: a SEPTA Regional Rail departures board for a named station, and enumerates exactly what is returned (train number, line, destination, scheduled vs estimated time, status, track). It is clearly not an alerts or vehicle-position tool, though it never names the closest sibling (septa_next_to_arrive) to draw the boundary explicitly.

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 departures-board framing implies the use case ("I want the next trains at station X"), and the worked example with a `results` value shows a realistic invocation. However, there is no explicit when-to-use vs when-not guidance and no named alternative, leaving the agent to infer the boundary with septa_next_to_arrive and septa_train_view.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.