Skip to main content
Glama

Bart Departures

bart_departures
Read-onlyIdempotent

Real-time BART San Francisco Bay Area train departures for a station, next train departure times in minutes, per destination, with platform, direction, train length (cars), line color, delay, and bikes allowed. Station accepts a 4-letter BART code ("EMBR", "SFIA") or a station name ("Embarcadero", "Downtown Berkeley", "SFO"). Answers "when is the next BART train". Example: bart_departures({ station: "Embarcadero" })

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": {
      "station": "EMBR"
    },
    "name": "bart_departures"
  }
}

Input Schema

NameRequiredDescriptionDefault
_apiKeyNoOptional: your own BART API key (defaults to the BART public key)
stationYesBART station, 4-letter code like "EMBR", "MONT", "SFIA", or a name like "Embarcadero", "Powell", "Downtown Berkeley"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / station / description
      Previous value: -"BART station — 4-letter code like \"EMBR\", \"MONT\", \"SFIA\", or a name like \"Embarcadero\", \"Powell\", \"Downtown Berkeley\""New value: +"BART station, 4-letter code like \"EMBR\", \"MONT\", \"SFIA\", or a name like \"Embarcadero\", \"Powell\", \"Downtown Berkeley\""
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "station": "EMBR"
      +  },
      +  {
      +    "station": "Downtown Berkeley"
      +  }
      +]
  3. First observed

TDQS

A4.1/5.0
Behavior4/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 that the data is real-time and enumerates what comes back (platform, direction, car count, line color, delay, bikes allowed), which is genuinely useful behavioral context. It stops short of saying how fresh or cached the data is and whether an unknown station errors or returns empty.

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?

Purpose and field list are front-loaded in the first sentence, followed by input formats and a worked example; every element is relevant. It is slightly dense as one long clause-chain rather than being broken into scannable points, but there is no filler.

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 two-parameter read with no output schema, the description carries the return-value burden well by listing the per-destination fields. Only minor omissions remain: no note on missing/unknown station behavior and no mention of the optional API-key parameter's tradeoffs.

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 description coverage is 100% and the schema already documents both the station formats and the optional _apiKey, so the description's restatement of the 4-letter-code-or-name convention adds no new meaning. Baseline 3 is the correct ceiling when the schema does the heavy lifting.

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?

Names a specific verb and resource ("Real-time BART ... train departures for a station") and states the scope and returned fields, which clearly separates it from bart_advisories, bart_stations, and bart_trip_planner. An agent can identify this as the departure-board tool without opening the 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 an explicit use case ("Answers 'when is the next BART train'") and a concrete invocation example, so the intended situation is clear. It does not state when *not* to use it or point to a sibling such as bart_trip_planner for routing, which is the only real gap.

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.