Skip to main content
Glama

BRAINIAC Geo & Environment Lookups

Compute next GTFS scheduled arrivals

geo-environment_gtfs-next-arrivals
Read-onlyIdempotent

Compute next scheduled arrivals at a stop from a caller-supplied static GTFS zip. No feeds are fetched. Price $0.04 USDC. POST /api/v1/geo-environment/gtfs-next-arrivals. An unpaid call returns the x402 payment terms and does not run.

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": {
      "gtfsZipBase64": "<gtfsZipBase64>",
      "stopId": "<stopId>",
      "at": "<at>"
    },
    "name": "geo-environment_gtfs-next-arrivals"
  }
}

Input Schema

NameRequiredDescriptionDefault
atYesat, string, length 10 to 40. Required.
limitNolimit, integer, from 1 to 50. Required.
stopIdYesstopId, string, length 1 to 120. Required.
gtfsZipBase64YesgtfsZipBase64, string, length 16 to 14000000. Required.
includeChildStopsNoincludeChildStops, boolean. Required.

Output Schema

NameRequiredDescriptionDefault
stopNostop. Object.
sourcesNosources. Array.
arrivalsNoarrivals. Array.
timeZoneNotimeZone. String.
warningsNowarnings. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive safety, so the description focuses on what annotations cannot express: the $0.04 USDC price and the x402 gating behavior where an unpaid call returns payment terms instead of results. That payment/auth disclosure is genuinely valuable operational context, though it omits rate limits or what happens on an invalid zip.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the action and scope before endpoint and pricing details. Every sentence carries distinct information—no restatement of the title or name.

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 an output schema present, return values need not be explained, and the description covers source, cost, transport, and failure mode for unpaid calls. Missing only marginal items such as behavior on malformed zip input or pagination of results up to the 'limit' cap.

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%, so parameter documentation is already handled. The description only implies that 'stopId' is a stop and 'at' is a time; it adds no format hints (e.g., timestamp format or zip encoding expectations) beyond what the schema states.

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 (compute next scheduled arrivals), the resource (a stop), and the data source (caller-supplied static GTFS zip), plus an explicit exclusion ('No feeds are fetched'). None of the sibling tools touch transit schedules, so the scope statement alone makes it unambiguous.

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?

The 'no feeds are fetched, caller-supplied zip' clause tells the agent what inputs must be supplied, which is implied usage guidance, but there is no explicit when-to-use or when-to-prefer-another-tool statement. Usage is inferable but not spelled out.

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