Skip to main content
Glama
Sign In
MBTA MCP Server

MBTA MCP Server

by cubismod
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

mbta_get_alerts

Retrieve MBTA service alerts and disruptions. Filter by route, stop, or specific alert ID to get current transit issues.

Instructions

Get MBTA service alerts and disruptions.

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_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
alert_idNoSpecific alert ID to get
route_idNoFilter alerts by route ID
stop_idNoFilter alerts by stop ID
page_limitNoNumber of results to return (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 MBTA service alerts and disruptions' without disclosing behavior like filtering, pagination, rate limits, or whether results are sorted. This is insufficient for a tool with 4 optional parameters.

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 very concise at one sentence, with no filler. It is front-loaded with the action, but it may be too brief to be helpful. Still, it earns points for brevity.

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 and no annotations, the description is incomplete. It does not explain what a typical response looks like, how alerts are structured, or how to interpret them. The tool has multiple optional filters but their combined effect is unstated.

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?

Input schema coverage is 100%, with all four parameters having descriptions (alert_id, route_id, stop_id, page_limit). The tool description adds no extra meaning beyond the schema, meeting the baseline. It does not enhance understanding of parameter usage.

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 clearly states the tool gets MBTA service alerts and disruptions, using a specific verb and resource. However, it does not differentiate from sibling tools like mbta_list_all_alerts or mbta_get_external_alerts, which have overlapping purposes.

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_alerts or mbta_get_external_alerts. The description lacks context for choosing this tool over siblings.

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

Deploy Server

Other Tools