Skip to main content
Glama

Live SEPTA regional rail train positions from the public

travel_septa_train_view
Read-only

Live SEPTA regional rail train positions from the public TrainView feed: train number, line, destination, current and next stop, heading, minutes late and track. Covers SEPTA regional rail trains currently reporting; not a schedule. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "travel_septa_train_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax trains returned, 1 to 200 (default 50)

Output Schema

NameRequiredDescriptionDefault
countNo
sourceNo
trainsNo
checkedAtNo
totalTrainsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds genuinely new behavior: per-successful-call pricing via x402 with multiple payment networks, and that failed calls are not charged. This is high-value cost/side-effect information absent from structured fields. It does not discuss rate limits or data freshness beyond 'currently reporting'.

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?

Purpose is front-loaded in the first sentence, followed by the scope caveat and then billing terms, so the agent hits the most important information first. The payment parenthetical is slightly long but carries decision-relevant cost detail rather than filler.

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?

With an output schema present, the description needn't explain return values, and annotations cover safety; the remaining gaps an agent needs (what data is live vs scheduled, cost model) are addressed. Nothing required to invoke this single-optional-parameter read tool is missing.

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?

The single 'limit' parameter is already fully documented in the schema (range 1-200, default 50) at 100% coverage, so the description needn't restate it. Baseline 3 applies; the description adds nothing about parameter meaning beyond the schema.

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?

States a specific resource and verb surface ('Live SEPTA regional rail train positions from the public TrainView feed') and enumerates the fields returned (train number, line, destination, current/next stop, heading, minutes late, track). The explicit caveat 'not a schedule' distinguishes it from schedule-oriented siblings such as train trackers that return timetables.

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?

Gives a clear inclusion condition ('Covers SEPTA regional rail trains currently reporting') and an exclusion ('not a schedule'), which is exactly the decision an agent needs. It does not name any alternative tool for schedule or other-agency queries, so routing to siblings is left to inference.

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.

Resources