Skip to main content
Glama

Commute lookup

commute_lookup
Read-onlyIdempotent

Commute from one Chicago-area residential address to downtown Chicago on one service date: drive to a Metra station (without traffic), station buffer and scheduled train, for up to 5 station options (nearest stations first), with sources and a methodology link.

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": "commute_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNoOptional. Fill only with facts the user volunteered. No names, contact details or chat text.
optionsNoHow many options to return, from 1 to 5, default 3. The nearest one or two stations are always included, so an answer can hold more options than requested.
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
address_idNo
componentsNo
terminal_idNo
address_textNo
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

A3.8/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so safety is covered. The description adds real value by disclosing the computation model (drive to station 'without traffic', station buffer, scheduled train) and the nearest-first ordering. It does not mention how results are constrained when windows conflict or how many requests a single call fans out to, leaving some operational behavior unstated.

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?

One dense sentence that front-loads the core action, with the output shape appended in a compact list. It is information-dense rather than padded, though a period-and-list structure would scan better than a single colon-chained sentence.

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?

Return values are covered by the output schema, so the description needn't explain them. For a 12-parameter tool with nested address components and a context object, the definition leaves direction/window/time-selection semantics entirely to the schema, which is acceptable but not fully complete on its own.

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?

With 12 parameters, nested objects, and only 33% schema description coverage, the description carries a real compensation burden. It only clarifies the options/nearest-first behavior and the address/date scope; direction, window_id, terminal_id, buffer_seconds, and the context object get nothing beyond the schema's own object-level text. Baseline 3 given the schema's detailed embedded descriptions.

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?

States a specific verb and resource (commute from one Chicago-area residential address to downtown Chicago on one service date) and enumerates the computed pieces: drive time, station buffer, scheduled train, up to 5 station options nearest-first, plus sources and methodology. The 'one address' framing cleanly distinguishes it from the batch sibling.

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 'one Chicago-area residential address ... on one service date' scoping implies the batch tool is for multiple addresses, which is useful routing context. However, no alternative is named explicitly and there is no statement of when not to use it (e.g., outbound-only trips or non-Chicago origins).

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