Skip to main content
Glama

Septa Next To Arrive

septa_next_to_arrive
Read-onlyIdempotent

Next SEPTA Regional Rail trains from an origin station to a destination station in Philly, direct trains and connecting itineraries (with transfer station), departure/arrival times, and live delay status. Answers "when is the next train from X to Y" in Philadelphia. Example: septa_next_to_arrive({ orig: "Suburban Station", dest: "Airport Terminal B", n: 3 })

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": {
      "dest": "Airport Terminal B",
      "orig": "Suburban Station"
    },
    "name": "septa_next_to_arrive"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNoHow many upcoming trains to return (default 3, max 10)
destYesDestination Regional Rail station, e.g. "Airport Terminal B", "Ardmore" (fuzzy-matched)
origYesOrigin Regional Rail station, e.g. "Suburban Station", "Fox Chase" (fuzzy-matched)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "dest": "Airport Terminal B",
      +    "orig": "Suburban Station"
      +  },
      +  {
      +    "dest": "Ardmore",
      +    "n": 5,
      +    "orig": "Fox Chase"
      +  }
      +]
  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 readOnly, idempotent, openWorld and non-destructive, and the description adds genuinely new context: results include both direct trains and connecting itineraries with the transfer station named, along with live delay status. It also constrains scope to Regional Rail only, which signals that bus/subway data is out of scope. It does not state what happens when a station name fails to fuzzy-match.

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?

Front-loaded with the core purpose in the first clause, followed by return content, the question it answers, and a compact example. No filler sentences; every element contributes to selection or invocation.

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 carries the burden of describing returns and does so at a useful level: itinerary types, transfer station, departure/arrival times, delay status. For a three-parameter read-only lookup with fully documented schema and annotations, this is nearly sufficient; only edge-case behavior for unmatchable station names is absent.

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 documents orig/dest as fuzzy-matched station names and n as count with default and max. The description's inline example merely re-demonstrates parameter shapes already present in the schema examples, adding no new semantics. 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 specific verb and resource: next Regional Rail trains from an origin to a destination, plus what the response contains (direct trains, connecting itineraries with transfer station, times, live delay status). Scope is narrowed to Philadelphia Regional Rail, which implicitly separates it from the bus/alert siblings, but no sibling is named 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?

Usage is conveyed indirectly through the framing question "when is the next train from X to Y" and a worked example, which makes the intent obvious. There is no explicit when-not guidance and no named alternative (e.g. septa_rail_arrivals for single-station arrival boards), so an agent must infer the boundary.

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.