Skip to main content
Glama

Commute lookup, batch

commute_lookup_batch
Read-onlyIdempotent

The same dated commute as commute_lookup for up to 10 Chicago-area addresses in one call, for comparing homes. Returns one result per address in request order; an address that cannot be answered gets its own error entry and the others still answer. Default 1 option per address.

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>",
      "addresses": "<addresses>"
    },
    "name": "commute_lookup_batch"
  }
}

Input Schema

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

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description usefully adds partial-failure semantics (per-address error entry, others still answer), result ordering, and the default option count. However, it does not disclose the time-window constraint the schema enforces or what a successful result entry looks like.

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?

Three sentences, front-loaded with the identity and scope, then the failure mode, then the default. Every sentence carries information; no 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?

Given an output schema exists and annotations cover the safety profile, the description supplies what those cannot: ordering, partial-failure behavior, and default option count. The main gap is that the exactly-one-of time-window rule lives only in the schema description.

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 10 parameters and only 40% schema description coverage, the description has room to compensate but only clarifies options (default 1 per address) and the address cap of 10. The window_id/arrive_by/depart_after/direction/terminal_id relationship and the context block are documented only in the schema's own top-level description.

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+resource (dated commute lookup), names the sibling it mirrors (commute_lookup), and adds the batch scope (up to 10 Chicago-area addresses) plus the use case (comparing homes). An agent can immediately tell this apart from the single-address 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?

"for comparing homes" gives clear context for choosing the batch form, and "the same dated commute as commute_lookup for up to 10 ... addresses in one call" implicitly routes single-address queries to the sibling. It stops short of an explicit when-not-to-use statement or naming station_info as an alternative.

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