Skip to main content
Glama

Bart Trip Planner

bart_trip_planner
Read-onlyIdempotent

Plan a BART trip between two Bay Area stations, the next trains from origin to destination with departure and arrival times, trip duration, legs (line, transfer stations, bikes), and the fare (Clipper and discount prices). Covers trips like SF to Oakland, Embarcadero to SFO airport, Berkeley to Millbrae. Stations accept 4-letter codes or names. Example: bart_trip_planner({ from: "Embarcadero", to: "SFIA" })

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": {
      "to": "SFIA",
      "from": "EMBR"
    },
    "name": "bart_trip_planner"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesDestination station, code or name, e.g. "SFIA" or "SFO airport"
fromYesOrigin station, code or name, e.g. "EMBR" or "Embarcadero"
tripsNoHow many upcoming trips to return, 1-4 (default 4)
_apiKeyNoOptional: your own BART API key (defaults to the BART public key)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / from / description
      Previous value: -"Origin station — code or name, e.g. \"EMBR\" or \"Embarcadero\""New value: +"Origin station, code or name, e.g. \"EMBR\" or \"Embarcadero\""
    • changedInput schema / properties / to / description
      Previous value: -"Destination station — code or name, e.g. \"SFIA\" or \"SFO airport\""New value: +"Destination station, code or name, e.g. \"SFIA\" or \"SFO airport\""
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "from": "EMBR",
      +    "to": "SFIA"
      +  },
      +  {
      +    "from": "Downtown Berkeley",
      +    "to": "Powell",
      +    "trips": 2
      +  }
      +]
  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 genuinely useful behavior beyond that: what the response contains (legs with line, transfer stations, bikes, Clipper and discount fares), which matters because there is no output schema. It does not mention the optional API-key fallback or any error behavior for unknown station names.

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?

Front-loaded with the core action and response contents, then station-format rules, then an example — a sensible order. It is slightly padded: three corridor examples followed by a separate example call is redundant, since one or the other would convey the same thing.

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?

With no output schema, the description correctly spends its words on return values (times, duration, legs, fares) rather than repeating annotations, which makes the definition usable as-is. The gaps are minor but real: the `trips` limit, the API-key default, and behavior on an unrecognized station name are all left to the schema or 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?

Schema coverage is 100%, so all four parameters are already documented, and the description largely restates the code-or-name convention the schema shows. It adds the specific detail that station codes are 4-letter and gives a canonical call example, but says nothing about the `trips` count or the `_apiKey` fallback. Baseline 3 is appropriate 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?

The description uses a specific verb+resource ("Plan a BART trip between two Bay Area stations") and immediately enumerates the scope: departure/arrival times, duration, legs, transfers, bikes, and fare. This scope (a full origin→destination itinerary with fare and transfer detail) implicitly separates it from a single-station departures tool, so an agent can identify the right 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?

Usage context is clear and concrete, with named corridors (SF to Oakland, Embarcadero to SFO, Berkeley to Millbrae) that show the intended call shape. There is no explicit when-not-to-use guidance or pointer to a sibling (e.g., bart_departures for single-station queries), which keeps it below a 5.

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.