Skip to main content
Glama

Mbta Stops

mbta_stops
Read-onlyIdempotent

List the stops and stations on an MBTA route, Boston subway T lines, commuter rail lines, bus routes, ferries. Returns stop id, name, municipality, and wheelchair accessibility, in route order. Example: mbta_stops({ route: "Red" }) or mbta_stops({ route: "CR-Worcester" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "route": "Red"
    },
    "name": "mbta_stops"
  }
}

Input Schema

NameRequiredDescriptionDefault
routeYesRoute id from mbta_routes, e.g. "Red", "Green-D", "CR-Providence", "66"
_apiKeyNoOptional: free MBTA v3 API key from api-v3.mbta.com for higher rate limits

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "route": "Red"
      +  },
      +  {
      +    "route": "CR-Providence"
      +  }
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, open-world), so the remaining burden is light. The description adds real behavioral context beyond them: which fields are returned (id, name, municipality, wheelchair accessibility) and that results come back in route order, which matters for sequence-dependent use.

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?

Two sentences: the first front-loads purpose and scope, the second delivers return fields, ordering, and examples. 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?

For a simple read-only lookup with no output schema, the description supplies the return shape and ordering, which the schema does not. The only gap is rate-limit/auth context, but the optional _apiKey parameter is documented in the schema.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds meaning by illustrating concrete route id values across modes ('Red', 'CR-Worcester'), which helps an agent understand the accepted id taxonomy beyond the schema's single parenthetical example.

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 verb and resource ('List the stops and stations on an MBTA route') and enumerates the route classes covered (subway T lines, commuter rail, bus, ferries). It does not explicitly differentiate itself from siblings like mbta_routes or mbta_departures, so it stops short of a 5.

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: the examples show the shape of a valid route id, and the schema notes the id comes from mbta_routes. There is no explicit statement of when to use this versus mbta_departures or mbta_routes, and no exclusions.

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.