Skip to main content
Glama

Station info

station_info
Read-onlyIdempotent

Facts about one Metra station on one service date, by station ID or name: its routes, the downtown Chicago terminals it serves and facility links when known.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "service_date": "<service_date>"
    },
    "name": "station_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
contextNoOptional. Fill only with facts the user volunteered. No names, contact details or chat text.
arrive_byNoA clock time on the service date (H:MM, HH:MM, or HH:MM:SS in America/Chicago) or an RFC 3339 date-time with an offset, for example 09:00, 2026-11-12T09:00:00-06:00, or 2026-11-12T15:00:00Z.
directionNo
window_idNo
station_idNo
terminal_idNo
depart_afterNoA clock time on the service date (H:MM, HH:MM, or HH:MM:SS in America/Chicago) or an RFC 3339 date-time with an offset, for example 09:00, 2026-11-12T09:00:00-06:00, or 2026-11-12T15:00:00Z.
service_dateYes
buffer_secondsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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=false, so the safety profile needs no restating. The description adds one genuinely useful behavioral note — facility links are returned 'when known', signalling partial/optional data — but says nothing about missing stations, ambiguous name resolution, or how errors surface.

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?

A single front-loaded sentence that names the resource, keying method, and return contents with no filler. It is efficient, if a little dense in the trailing clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the schema's own object description covers the XOR and direction-default rules. Still, for a 10-parameter tool with rich routing semantics, the description contributes little beyond the one-line summary.

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

Parameters2/5

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

Schema description coverage is only 30% across 10 parameters (2 enums, one nested object). The description only covers station_id/name and service_date; it gives no meaning for direction, terminal_id, window_id, arrive_by, depart_after, buffer_seconds, or the context block, leaving the compensation burden unmet.

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?

States a specific resource and scope: facts about ONE Metra station on ONE service date, keyed by station ID or name, returning routes, downtown terminals, and facility links. An agent can immediately tell this is a per-station fact lookup rather than a trip/commute query, though the description never names the sibling tools it differs from.

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 by the framing (single station, single service date); there is no explicit when-to-use, when-not, or pointer to commute_lookup / commute_lookup_batch as the alternative for itinerary-style questions. An agent must infer the boundary between station facts and commute planning.

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