Skip to main content
Glama

Mbta Alerts

mbta_alerts
Read-onlyIdempotent

Active MBTA service alerts, Boston subway T delays, commuter rail disruptions, shuttle replacements, track changes, detours, elevator outages. Filter by route to check one line, e.g. is the Red Line delayed right now. Example: mbta_alerts({ route: "Red" })

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax alerts to return, 1-50 (default 15)
routeNoOptional route id to filter, e.g. "Red", "CR-Kingston", "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"
      +  },
      +  {
      +    "limit": 20
      +  }
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds the meaningful behavioral scope (only ACTIVE alerts, category coverage), but says nothing about rate limits, the effect of the optional API key, or pagination/bounding behavior.

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?

Front-loaded with what the tool returns, followed by filtering guidance and a compact example. The category list is long but each item is informative rather than filler; nothing is repeated.

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 three-optional-parameter read tool with full annotation coverage and no output schema, the definition conveys what comes back (a set of active alerts) and how to narrow it. The main omission is any hint about the shape/ordering of results or the 'active' time window.

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 all three parameters are already documented in the schema. The description reinforces the route filter with a worked example and a real route id ('Red'), but adds no syntax, enum, or limit semantics beyond what the schema provides.

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 resource ('Active MBTA service alerts') and enumerates the alert categories returned (delays, shuttle replacements, track changes, detours, elevator outages), which is far more concrete than the name alone. It does not distinguish itself from the sibling 'recent_alerts', leaving the boundary between 'active' and 'recent' ambiguous.

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 a clear triggering scenario — 'filter by route to check one line, e.g. is the Red Line delayed right now' — plus a concrete call example. It stops short of exclusions or naming an alternative for historical/recent alert lookups.

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.