Skip to main content
Glama

Live Amtrak train status from Amtrak's Track Your Train map

travel_amtrak_train_tracker
Read-only

Live Amtrak train status from Amtrak's Track Your Train map feed: train number, route, origin/destination, state (Predeparture/Active/Completed), current GPS position, speed (mph), heading, last update, and every stop with scheduled and estimated/actual arrival and departure plus on-time/late comments. Filter by train number, route name or station code. 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_amtrak_train_tracker"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoTrains, 1 to 200 (default 20)
routeNoRoute name contains, e.g. Zephyr, Acela, Northeast Regional
stateNoActive, Predeparture or Completed
stationNoOnly trains stopping at this station code, e.g. CHI, NYP, LAX
trainNumNoTrain number, e.g. 5 (California Zephyr)

Output Schema

NameRequiredDescriptionDefault
totalNo
sourceNo
trainsNo
checkedAtNo
feedTrainsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds genuinely new behavioral context — a per-call price of $0.002, an x402/USDC payment mechanism across multiple networks, and the fact that failed calls are free. That billing detail is decision-relevant for an agent and is not derivable from structured fields, though freshness/pagination or rate-limit behavior is not covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and pricing are front- and back-loaded sensibly, but the middle is a long comma-chained enumeration of returned fields that largely duplicates the existing output schema. Trimming that run-on list would make the definition tighter without losing decision-relevant information.

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 an output schema present, the description needn't explain return shapes, and between the annotations and the pricing note an agent has enough to invoke it safely. The remaining gap is coverage and freshness expectations (e.g. how stale 'last update' can be, whether all Amtrak routes are tracked).

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 coverage is 100%, so every one of the five parameters already carries its own description and example values. The description restates the filterable dimensions at a high level ('train number, route name or station code') without adding format or matching semantics beyond the schema, so the baseline 3 applies.

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 verb and resource ('Live Amtrak train status from Amtrak's Track Your Train map feed') and enumerates the payload: train number, route, state, GPS position, speed, heading and per-stop times. Naming Amtrak and its specific map feed cleanly separates it from sibling transit tools such as travel_septa_train_view or travel_flightradar24_live_flights.

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 description tells the agent how to narrow results ('Filter by train number, route name or station code'), which implies the lookup use case, but it never states when to prefer this tool over a sibling tracker or what to do when no filter matches. Usage is inferred rather than instructed.

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