Skip to main content
Glama

transitpulse

Evaluate global public transit routes with reliability, delay predictions, and multi-modal trip planning across 500+ cities. Optimize commutes and compare city transit systems.

Instructions

TransitPulse: TransitPulse — global public transit intelligence: route reliability, delay prediction, multi-modal trip planning, city transit scores, and commute optimization for 500+ cities worldwide.

Coverage: Global

Endpoints: • status ($0.10): Live Service Status • city ($0.10): City Transit Intelligence Brief • route ($0.10): Route Reliability Analysis • commute ($0.10): Commute Quality Analysis • airport ($0.10): Airport Transit Guide • agencies ($0.10): Transit Agencies Lookup • delays ($0.10): Current Transit Delays • delays-history ($0.10): Historical Delay Patterns • trip ($0.10): Transit Trip Planning • multimodal ($0.10): Multi-Modal Journey Planning • compare ($0.10): City-to-City Transit Comparison • carfree ($0.10): Car-Free Livability Score • visitor ($0.10): First-Timer Visitor Guide • coverage ($0.10): Transit Coverage Analysis

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesWhich endpoint to call. Options: status | city | route | commute | airport | agencies | delays | delays-history | trip | multimodal | compare | carfree | visitor | coverage
langNoResponse language code (en | es | fr | de | zh | hi | ar | pt | ja | ko | etc.)
cityNoCity name (e.g. London, NYC, Tokyo)
lineNoSpecific line or route to focus on
routeNoLine or route name (e.g. L train, Northern line)
timeNoTime of travel (e.g. 9am, rush hour)
fromNoOrigin neighborhood or address
toNoDestination neighborhood or address
airportNoIATA code (JFK, LHR) or name
flight_timeNoFlight departure time (e.g. 6am)
city_aNoFirst city
city_bNoSecond city
citiesNoAlternative: comma-separated pair (e.g. NYC,London)
neighborhoodNoneighborhood
Behavior3/5

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

With no annotations, the description carries the full burden. It mentions pricing per endpoint and provides brief endpoint descriptions (e.g., 'Live Service Status'), but does not disclose rate limits, data freshness, authentication needs, or whether the tool mutates anything. As a read-only data tool, that context is valuable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured with bullet points and front-loaded purpose, but includes pricing details that may not be essential for tool selection. It is longer than necessary, though the structure helps readability.

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?

Given the tool's complexity (14 parameters, 14 actions, no output schema), the description adequately covers the available actions but lacks guidance on parameter combinations (e.g., which parameters are needed for each action) and does not describe return values.

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%. The description adds marginal value by associating each action enum value with a one-line description and price, which helps disambiguate the purpose of each action beyond the schema's bare descriptions.

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?

Description clearly states 'global public transit intelligence' and lists endpoints covering route reliability, trip planning, etc. However, it does not differentiate from sibling tools like alphapulse or travelpulse, which likely cover other domains.

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?

No guidance on when to use this tool versus alternatives (e.g., travelpulse). The description lists endpoints but does not explain which action to choose for a given user request, nor does it provide prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GTCC777/pulsenetwork-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server