Skip to main content
Glama

Amtrak Routes Active

amtrak_routes_active
Read-onlyIdempotent

Summary of ALL currently active Amtrak trains grouped by route, "how many Amtrak trains are running right now", "which Amtrak routes have delays", national system overview. Returns per route: active train count, train numbers, and the worst delay in minutes. Compact; live from a community mirror of Amtrak's tracking feed. Example: amtrak_routes_active({})

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": {},
    "name": "amtrak_routes_active"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, and the description goes further by disclosing data provenance ('live from a community mirror of Amtrak's tracking feed'), freshness ('currently active', 'live'), and payload size ('compact'). It does not discuss rate limits or reliability caveats of the mirror, which keeps it at 4.

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 scope and key example queries are front-loaded, and the return fields are listed compactly in one clause. The trailing example invocation is mildly redundant given the empty schema, but overall there is little wasted text.

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 carries the return-shape burden and does so by naming active train count, train numbers, and worst delay per route. For a zero-parameter read-only list tool that is essentially complete, missing only minor details such as ordering or whether delayed routes are flagged.

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?

The tool takes zero parameters, so no parameter explanation is required and the empty-object example call reinforces that. Baseline for a no-parameter tool is 4; nothing here adds or detracts from parameter meaning.

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 names a concrete resource and scope: 'Summary of ALL currently active Amtrak trains grouped by route' with a national system overview, plus the per-route fields returned. It implicitly separates itself from station- and train-level siblings via the ALL/national scope, but never names an alternative tool, so it falls short of a 5.

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?

Three representative user intents are quoted (how many trains are running, which routes have delays, national overview), which gives an agent clear context for selecting this tool. There is no explicit when-not guidance or pointer to the station/train siblings, so it stops at 4.

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.