Skip to main content
Glama

Mbta Routes

mbta_routes
Read-onlyIdempotent

List MBTA routes for the Boston subway T, commuter rail, bus, and ferry, route ids, names, and the destination each direction heads toward. type: 0-1 subway/light rail (Red, Orange, Blue, Green, Mattapan), 2 commuter rail, 3 bus (includes Silver Line), 4 ferry. Default returns subway + commuter rail + ferry; pass type 3 for buses. Example: mbta_routes({ type: "2" })

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": {
      "type": "2"
    },
    "name": "mbta_routes"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoRoute type filter, comma-separable: "0,1" subway, "2" commuter rail, "3" bus, "4" ferry (default "0,1,2,4")
_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: +[
      +  {
      +    "type": "2"
      +  },
      +  {
      +    "type": "0,1"
      +  }
      +]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds real behavior beyond that: the exact default type set returned when no filter is passed and what each result contains. It omits rate-limit/pagination behavior, but the API-key note lives in the schema.

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?

Front-loaded with the verb and scope, then the type taxonomy, then default behavior and a concrete example call. Some redundancy with the schema's own type description, but every sentence still earns its place and nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does so ('route ids, names, and the destination each direction heads toward'). Combined with the default-scope statement and a worked example, an agent has everything needed to call this correctly on first try.

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 a 3 would be the baseline, but the description meaningfully expands the 'type' semantics — decomposing 0-1 into Red, Orange, Blue, Green and Mattapan lines and noting Silver Line counts as bus type 3. That is domain knowledge the schema's terse enum string does not convey.

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 (list MBTA routes) plus the covered modes (subway/T, commuter rail, bus, ferry) and the fields returned (route ids, names, per-direction destinations). This is clearly distinguishable from sibling tools like mbta_stops and mbta_departures without opening a schema.

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?

Gives actionable selection guidance: the default returns subway + commuter rail + ferry, and 'pass type 3 for buses' tells the agent exactly how to widen scope. It stops short of naming when to prefer a sibling tool (e.g., stops or departures) or stating exclusions, so it does not reach a 5.

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.