Skip to main content
Glama

Bart

by io.github.pipeworx-io

Bart Stations

bart_stations
Read-onlyIdempotent

List all 50 BART San Francisco Bay Area train stations with 4-letter code, full name, city, street address, and coordinates. Optional filter matches station name or city (e.g. "Oakland", "Berkeley", "airport"). Use to find the station code for departures, trips, or fares. Example: bart_stations({ filter: "San Francisco" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNoOptional name or city filter, e.g. "Oakland", "airport", "Mission"
_apiKeyNoOptional: your own BART API key (defaults to the BART public key)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "filter": "Oakland"
+  },
+  {}
+]
  2. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint false. Description adds return fields but no additional behavioral traits beyond annotations.

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?

Two sentences with no waste. Front-loaded with action, includes example call. Every sentence adds value.

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

Completeness5/5

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

Lists all output fields (code, name, city, address, coordinates). Explains filtering. Since no output schema exists, description fully explains return values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers both parameters (100% coverage). Description adds extra context with example usage and clarifies filter matches station name or city, going beyond schema descriptions.

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 specific verb 'List' and resource 'all 50 BART stations' with clear output fields. It distinguishes from sibling tools like bart_departures by stating its purpose for finding station codes.

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?

Explicitly states 'Use to find the station code for departures, trips, or fares.' Provides a concrete example with filter parameter, but does not explicitly mention when not to use.

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

All Bart toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but the three ask_pipeworx variants (stable, beta, grounded) overlap significantly in functionality, as do the Polymarket tools (bet_research, arbitrage, edges, etc.), which could cause an agent to misselect without careful reading of descriptions.

Naming Consistency3/5

Naming follows multiple styles: verb_noun (ask_pipeworx, compare_entities), domain first (polymarket_arbitrage, bart_departures), and single words (remember, forget). There is no consistent pattern, making the set feel disjointed.

Tool Count3/5

35 tools is on the heavy side for a single server. While each tool has a defined role, the count suggests potential for consolidation (e.g., merging ask_pipeworx variants or Polymarket tools). The server's broad scope partially justifies the count.

Completeness4/5

The tool surface covers a wide range of functionalities: structured querying, entity lookup, comparison, fact-checking, subscription management, memory, and domain-specific tools for BART and Polymarket. Minor gaps exist (e.g., no direct API for some data sources), but overall it feels comprehensive.

Resources