MBTA MCP Server

Overview Schema Source Related Servers Discussions Admin

mbta_get_facilities

Retrieve facility details such as elevators, escalators, and parking for MBTA stops. Filter by facility type, stop ID, or specific facility ID.

Instructions

Get facility information (elevators, escalators, parking).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

Name	Required	Description
`facility_id`	No	Specific facility ID to get
`stop_id`	No	Filter facilities by stop ID
`facility_type`	No	Filter by facility type (ELEVATOR, ESCALATOR, PARKING_AREA, etc.)
`page_limit`	No	Number of results to return (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 26, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are present, so the description carries full burden. It merely states 'Get facility information' without disclosing any behavioral traits like read-only nature, potential side effects, or whether it returns static vs. live data. This is insufficient.

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?

The description is a single concise sentence that front-loads the action and resource. It is efficient, though slightly under-specified.

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

Completeness2/5

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

Given no output schema, no annotations, and four parameters, the description does not explain return format, pagination, or behavior when no parameters are provided. It lacks completeness for a tool of this complexity.

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?

All four parameters have descriptions in the input schema (100% coverage), so the description adds no additional meaning. Baseline of 3 is appropriate.

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?

The description clearly states the verb 'Get' and the resource 'facility information' with specific examples (elevators, escalators, parking). This distinguishes it from siblings like 'mbta_list_all_facilities' which lists all facilities, and 'mbta_get_live_facilities' which implies real-time data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives such as 'mbta_list_all_facilities' or 'mbta_get_live_facilities'. There are no exclusions or context hints for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.