Skip to main content
Glama

Amtrak Station Board

amtrak_station_board
Read-onlyIdempotent

Amtrak station departures/arrivals board, upcoming trains at a station. "What trains are arriving at Chicago Union?", "next train at CHI", "station board for Denver". Accepts a 3-letter Amtrak station code ("CHI", "NYP", "LAX") or a station name ("Chicago", "Portland"). Returns trains currently en route to that station with route, scheduled vs estimated arrival, delay minutes, and status. Live community mirror of Amtrak tracking (api-v3.amtraker.com). Example: amtrak_station_board({ station: "CHI" })

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": {
      "station": "CHI"
    },
    "name": "amtrak_station_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax trains to return, 1-15 (default 15)
stationYesAmtrak station code (e.g. "CHI", "NYP", "SEA") or station/city name (e.g. "Chicago", "Denver")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "station": "CHI"
      +  },
      +  {
      +    "limit": 10,
      +    "station": "Denver"
      +  }
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, open-world and non-destructive behavior, so the bar is lower, yet the description still adds real value: it discloses the upstream source (live community mirror at api-v3.amtraker.com) and the key scope constraint that only trains currently en route to the station are returned. It does not discuss data staleness, coverage gaps, or failure modes of the community mirror, which keeps it short of a 5.

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?

The capability statement and return contents are front-loaded, which is the right ordering. The three quoted example queries plus a separate example invocation are slightly redundant with one another and with the schema examples, adding a bit of bulk without new 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 no output schema, the description usefully enumerates the returned fields (route, scheduled vs estimated arrival, delay minutes, status) and states the input formats, so an agent knows what it will get back. Completeness is only mildly undercut by the absence of pagination/limit behavior and any note on how fresh the mirror data is.

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%, so both parameters are already documented, and the description largely restates the station format (3-letter code or city name) that the schema already gives. The optional 'limit' parameter is never mentioned in the description, so no meaning is added beyond the structured fields; 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?

The description names a specific resource and scope: an Amtrak station departures/arrivals board showing upcoming trains at one station. The example utterances ('next train at CHI', 'station board for Denver') make it operationally distinct from a single-train lookup such as amtrak_train_status and from station metadata such as amtrak_station_info, so an agent can route correctly without opening a schema.

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?

Usage is conveyed through concrete natural-language query patterns the tool is meant to answer, plus a worked call example, which clearly signals the intended context. It stops short of explicit when-not guidance or naming an alternative tool for adjacent needs (e.g. single-train status), leaving that inference to the agent.

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.