Skip to main content
Glama
Sign In
MBTA MCP Server

MBTA MCP Server

by cubismod
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

mbta_list_all_alerts

Retrieve all current MBTA alerts, with optional fuzzy search to filter by header or description.

Instructions

List all MBTA alerts with optional fuzzy filtering. Returns all alerts without specific filters, with client-side fuzzy search.

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

Input Schema

NameRequiredDescriptionDefault
queryNoOptional fuzzy search query to filter alerts by header or description
max_resultsNoMaximum number of results to return (default: 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description bears full responsibility for disclosing behavior. It only mentions 'client-side fuzzy search' and default behavior, omitting details like authentication, rate limits, data freshness, or error handling. This is insufficient for an accurate behavioral model.

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?

The description is two sentences long, with the most important information (verb, resource, optional filtering) in the first sentence. Every word is functional, and there is no redundancy or unnecessary detail.

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

Completeness3/5

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

For a simple list tool with no output schema and two intuitive parameters, the description captures the core functionality. However, it lacks details on output structure, default sorting, or limits, which could leave an agent uncertain about what to expect from the response.

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?

The input schema already describes both parameters (query, max_results) with 100% coverage. The description adds the phrase 'optional fuzzy filtering' and 'client-side fuzzy search,' which aligns with the query parameter but does not provide additional semantic meaning beyond the schema.

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 'List all MBTA alerts with optional fuzzy filtering,' specifying the verb and resource. However, it does not explicitly differentiate from sibling tools like mbta_get_external_alerts, which may have overlapping functionality.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, exclusions, or scenarios where other tools (e.g., mbta_get_alerts) would be more appropriate.

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