Skip to main content
Glama

Amtrak Station Info

amtrak_station_info
Read-onlyIdempotent

Amtrak station lookup by code or name, station name, 3-letter code, city/state, street address, timezone, coordinates, and how many trains are currently inbound. "Where is the Amtrak station in Denver?", "what is station code NYP". Example: amtrak_station_info({ station: "Denver" })

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": "NYP"
    },
    "name": "amtrak_station_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
stationYesAmtrak station code (e.g. "DEN", "NYP") or station/city name (e.g. "Denver", "New York")

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds useful disclosure of the response fields (name, code, city/state, address, timezone, coordinates, inbound train count), but says nothing about error behavior for unknown stations or result uniqueness.

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?

Front-loaded with the core action and the returned fields, then two illustrative queries and a call example. The trailing field enumeration is slightly list-heavy but every element carries information; nothing is repetitive filler.

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 one required parameter, full schema coverage, and no output schema, the description usefully compensates by enumerating the returned fields an agent would otherwise not know. Minor gaps remain around ambiguous-name handling and failure cases, but the definition is sufficient to call correctly.

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 single parameter already documents both accepted forms (code or city/name) with examples. The description and inline examples reinforce that flexibility but add no new syntax, matching, or ambiguity-resolution guidance, so the 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?

The opening clause names a specific verb and resource ("Amtrak station lookup by code or name") and enumerates the data returned, so an agent knows exactly what it gets back. It stops short of naming or contrasting a sibling such as amtrak_station_board, so it is clear but not fully differentiated.

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 only implied through example natural-language questions ("Where is the Amtrak station in Denver?") and a call example. There is no explicit statement of when to prefer this over the station board or train status tools, and no exclusions or prerequisites.

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.