Skip to main content
Glama

Live MBTA Boston vehicle positions for one route: vehicle

travel_mbta_realtime
Read-only

Live MBTA Boston vehicle positions for one route (e.g. Red, Orange, Blue, 1): vehicle label, latitude/longitude, bearing, speed, current status, current stop id and occupancy when reported. Anonymous access is rate limited by MBTA. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax vehicles, 1 to 100 (default 20)
routeYesMBTA route id, letters/digits/hyphens, 1 to 20 characters

Output Schema

NameRequiredDescriptionDefault
countNo
routeNo
sourceNo
vehiclesNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses meaningful operational facts: MBTA rate-limits anonymous access, calls cost $0.002 paid via x402 across several networks, and failed calls are not charged. It also flags that occupancy is only present 'when reported', which sets expectations on partial data. It does not describe pagination or how the limit interacts with results.

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?

Two dense sentences, front-loaded with the core purpose before the commercial/rate-limit details. Every clause carries information; only the enumeration of payment networks is borderline padding for an agent deciding whether to call the tool.

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, the description does not need to explain return structure, and annotations already cover the read-only safety profile. Coverage of pricing, rate limits, and data completeness (occupancy 'when reported') makes it sufficient for correct invocation, with only result-volume/pagination behavior left implicit.

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 coverage is 100%, so both route and limit are already documented in structured form, giving a baseline of 3. The description adds a small amount of value by giving concrete route examples (Red, Orange, Blue, 1) that illustrate the expected route-id format, but the limit parameter and its range are left entirely to the schema.

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 specific verb and resource: live vehicle positions for a single MBTA route, and lists the returned fields (label, lat/lon, bearing, speed, status, stop id, occupancy). It is unambiguous enough to separate from unrelated travel siblings such as travel_hk_mtr_realtime, but it never explicitly contrasts itself with other transit feeds.

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 implied rather than stated: the tool is for one route at a time, and the route examples (Red, Orange, Blue, 1) hint at when it fits. There is no explicit when-to-use/when-not guidance and no alternative named for multi-route or schedule queries.

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