Skip to main content
Glama

Amtrak Train Status

amtrak_train_status
Read-onlyIdempotent

Live Amtrak train status and GPS tracking, "where is my Amtrak train", "is train 6 late", "track the California Zephyr". Accepts a train number ("6", "2150") or route name ("Coast Starlight", "Empire Builder"). Returns each active instance of that train: current GPS position, speed, heading, timeliness, next station with ETA and delay minutes, and origin/destination scheduled vs actual times. Data is a community mirror of Amtrak's own tracking feed (api-v3.amtraker.com); positions update about every few minutes. Example: amtrak_train_status({ train: "6" })

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": {
      "train": "6"
    },
    "name": "amtrak_train_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
trainYesAmtrak train number (e.g. "6", "91", "2150") or route name (e.g. "California Zephyr", "Acela", "Coast Starlight"). Via Rail ("v1") and Brightline ("b5151") trains in the same feed also work.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "train": "6"
      +  },
      +  {
      +    "train": "California Zephyr"
      +  }
      +]
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive behavior, and the description adds substantial context beyond that: the data is a community mirror of api-v3.amtraker.com and positions refresh roughly every few minutes, which tells the agent the data may be stale or unofficial. It also discloses that multiple active instances of a train can be returned, so the agent knows to expect a list rather than a single record.

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?

It is front-loaded with the core purpose, then the accepted inputs, then the return shape, then a data-provenance caveat and example call — a logical order with no filler sentences. The cluster of quoted example queries is slightly repetitive, keeping it off a 5.

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?

There is no output schema, and the description compensates fully by enumerating the returned fields (GPS position, speed, heading, timeliness, next station ETA and delay minutes, origin/destination scheduled vs actual). Combined with the freshness and source caveats, an agent has everything needed to call it and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning: a train number ("6", "2150") and a route name ("Coast Starlight") are both accepted, and a route name resolves to every active instance of that train. That multiplicity with the worked example is genuine semantics beyond the schema text.

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?

The description states a specific verb and resource: live train status plus GPS tracking for a given Amtrak train, reinforced by the natural-language queries it answers ("where is my Amtrak train", "is train 6 late"). It is functionally distinct from the station/routes siblings, but it never names an alternative tool, so differentiation is inferred rather than stated.

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?

The quoted user questions ("where is my Amtrak train", "is train 6 late", "track the California Zephyr") give clear conditions for when this tool applies, and the sample call shows the expected invocation shape. There is no explicit when-not guidance or pointer to amtrak_station_board / amtrak_routes_active for station-level or route-level questions.

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.