Skip to main content
Glama

Septa Train View

septa_train_view
Read-onlyIdempotent

Live positions of every SEPTA Regional Rail train currently running in the Philadelphia region, train number, line, destination, current and next stop, minutes late, and lat/lon. Answers "is my train late" and "where is train 456". Optionally filter to one line. Example: septa_train_view({ line: "Paoli/Thorndale" })

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": {
      "line": "Paoli/Thorndale"
    },
    "name": "septa_train_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
lineNoOptional Regional Rail line filter: Airport, Chestnut Hill East, Chestnut Hill West, Cynwyd, Fox Chase, Lansdale/Doylestown, Manayunk/Norristown, Media/Wawa, Paoli/Thorndale, Trenton, Warminster, West Trenton, Wilmington/Newark. Omit for all live trains.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "line": "Paoli/Thorndale"
      +  },
      +  {}
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: this is a live snapshot of trains currently running, enumerates the returned fields (line, destination, current/next stop, minutes late, lat/lon), and clarifies that omitting the filter returns everything. It says nothing about refresh cadence, data staleness, or empty-result behavior.

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?

Front-loaded with the core purpose, then the returned fields, then the optional filter and an example. Dense and mostly waste-free, though the quoted-question framing and the trailing example overlap somewhat with the use-case sentence.

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 a single fully-documented parameter and no output schema, the description correctly carries the burden of describing return contents and real-time semantics, which it does. Missing only peripheral details like refresh rate or empty/no-trains behavior, so it is adequate for this complexity.

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% and the schema already enumerates every valid line name plus the 'omit for all live trains' default. The description only restates that the filter is optional and gives one example value, adding little meaning beyond the schema — 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?

States a concrete resource with scope: live positions of every SEPTA Regional Rail train currently running in the Philadelphia region, plus the exact fields returned and a sample call. It implicitly separates itself from bus-position and arrivals-style siblings by naming 'Regional Rail' and 'currently running', but never explicitly contrasts with septa_rail_arrivals or septa_next_to_arrive.

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

Usage Guidelines4/5

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

Frames the use cases concretely ('is my train late', 'where is train 456') and tells the agent the line filter is optional, with an example invocation showing the default (omit for all live trains). No when-not guidance or named alternatives, so it stops short of full routing guidance.

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.