pulsenetwork

transitpulse

TransitPulse: TransitPulse — global public transit intelligence: route reliability, delay prediction, multi-modal trip planning, city transit scores, and commute optimization for 500+ cities worldwide. NEW: rail/coach/ferry/cruise compensation recovery engine — UK Delay Repay, EU Rail 2021/782, ferry 1177/2010, coach 181/2011, US FMC cruise refunds, Athens Convention baggage — deterministic eligibility ($0.10) + citation-locked claim letters ($2.00).

Coverage: Global

Endpoints: • status ($0.05): Live Service Status • city ($0.08): City Transit Intelligence Brief • route ($0.08): Route Reliability Analysis • commute ($0.10): Commute Quality Analysis • airport ($0.08): Airport Transit Guide • agencies ($0.05): Transit Agencies Lookup • delays ($0.05): Current Transit Delays • delays-history ($0.08): Historical Delay Patterns • trip ($0.05): Transit Trip Planning • multimodal ($0.10): Multi-Modal Journey Planning • compare ($0.12): City-to-City Transit Comparison • carfree ($0.12): Car-Free Livability Score • visitor ($0.08): First-Timer Visitor Guide • coverage ($0.10): Transit Coverage Analysis • check ($0.05): Rail/Coach/Ferry/Cruise Compensation Eligibility Check • letter ($2.00): Citation-Locked Transit Compensation Claim Letter

Input Schema

TableJSON Schema

Name	Required	Description
`to`	No	Destination neighborhood or address
`city`	No	City name (e.g. London, NYC, Tokyo; default: London)
`from`	No	Origin neighborhood or address
`lang`	No	Letter language (default English)
`line`	No	Specific line or route to focus on
`mode`	No	Transport mode
`time`	No	Time of travel (e.g. 9am, rush hour)
`cause`	No	Disruption cause (default unknown — exemption burden is the operator's)
`route`	No	Line or route name (e.g. L train, Northern line)
`action`	Yes	Which endpoint to call. Options: status \| city \| route \| commute \| airport \| agencies \| delays \| delays-history \| trip \| multimodal \| compare \| carfree \| visitor \| coverage \| check \| letter
`cities`	No	Alternative: comma-separated pair (e.g. NYC,London)
`city_a`	No	First city
`city_b`	No	Second city
`scheme`	No	UK operator Delay Repay threshold (default DR30, conservative)
`airport`	No	IATA code (JFK, LHR) or name
`country`	No	ISO country of the journey/scheme (GB, FR, DE, US, CA, IN, JP, ... or EU)
`corridor`	No	Canada VIA: journey on the Quebec City-Windsor Corridor
`currency`	No	Ticket currency ISO code
`operator`	No	Operator/carrier name for the letter
`travelled`	No	India TDR + FMC cruise refunds require you did NOT travel
`delay_days`	No	Cruise: voyage delay in calendar days (FMC 3-day rule)
`disruption`	No	Disruption type (default delay)
`claim_value`	No	Ship baggage: documented damages with currency
`distance_km`	No	Coach: scheduled service distance (Reg 181/2011 applies from 250 km)
`flight_time`	No	Flight departure time (e.g. 6am)
`ticket_type`	No	UK Delay Repay percentages differ by ticket type
`journey_date`	No	YYYY-MM-DD — computes claim deadlines (UK 28 days, ferry 2 months, coach 3 months, JR 1 year)
`neighborhood`	No	neighborhood
`ticket_price`	No	Fare paid — percentage regimes compute the amount from this
`delay_minutes`	No	Arrival delay in minutes (rail/ferry); DEPARTURE delay for coach
`choice_offered`	No	Coach: did the carrier offer the refund/re-routing choice — the 50% turns on this
`disembark_date`	No	Ship baggage: disembarkation date (Athens Art. 15 notice window + Art. 16 bar)
`passenger_name`	No	Passenger name (placeholder if omitted)
`service_number`	No	Train/sailing/coach identifier
`damage_apparent`	No	Ship baggage (cabin): was the damage apparent at disembarkation
`express_surcharge`	No	Japan JR: limited-express surcharge paid (the refundable component)
`scheduled_journey_hours`	No	Ferry: scheduled crossing duration — selects the Art. 19 band

Schema Changelog

Changes observed during successful MCP inspections.

Changed24 schema fields changedJul 8, 2026

changedInput schema / properties / action / description

Previous value: -"Which endpoint to call. Options: status | city | route | commute | airport | agencies | delays | delays-history | trip | multimodal | compare | carfree | visitor | coverage | rights_check | rights_letter"New value: +"Which endpoint to call. Options: status | city | route | commute | airport | agencies | delays | delays-history | trip | multimodal | compare | carfree | visitor | coverage | check | letter"

changedInput schema / properties / action / enum

Previous value: -[
-  "status",
-  "city",
-  "route",
-  "commute",
-  "airport",
-  "agencies",
-  "delays",
-  "delays-history",
-  "trip",
-  "multimodal",
-  "compare",
-  "carfree",
-  "visitor",
-  "coverage",
-  "rights_check",
-  "rights_letter"
-]New value: +[
+  "status",
+  "city",
+  "route",
+  "commute",
+  "airport",
+  "agencies",
+  "delays",
+  "delays-history",
+  "trip",
+  "multimodal",
+  "compare",
+  "carfree",
+  "visitor",
+  "coverage",
+  "check",
+  "letter"
+]

addedInput schema / properties / cause

Added value: +{
+  "description": "Disruption cause (default unknown — exemption burden is the operator's)",
+  "type": "string"
+}

addedInput schema / properties / choice_offered

Added value: +{
+  "description": "Coach: did the carrier offer the refund/re-routing choice — the 50% turns on this",
+  "type": "string"
+}

addedInput schema / properties / claim_value

Added value: +{
+  "description": "Ship baggage: documented damages with currency",
+  "type": "string"
+}

addedInput schema / properties / corridor

Added value: +{
+  "description": "Canada VIA: journey on the Quebec City-Windsor Corridor",
+  "type": "string"
+}

changedInput schema / properties / country / description

Previous value: -"ISO country of the journey/scheme (GB, FR, US, CA, IN, JP, ... or EU)"New value: +"ISO country of the journey/scheme (GB, FR, DE, US, CA, IN, JP, ... or EU)"

addedInput schema / properties / currency

Added value: +{
+  "description": "Ticket currency ISO code",
+  "type": "string"
+}

addedInput schema / properties / damage_apparent

Added value: +{
+  "description": "Ship baggage (cabin): was the damage apparent at disembarkation",
+  "type": "string"
+}

addedInput schema / properties / delay_days

Added value: +{
+  "description": "Cruise: voyage delay in calendar days (FMC 3-day rule)",
+  "type": "string"
+}

changedInput schema / properties / delay_minutes / description

Previous value: -"Arrival delay in minutes (rail/ferry); departure delay for coach"New value: +"Arrival delay in minutes (rail/ferry); DEPARTURE delay for coach"

addedInput schema / properties / disembark_date

Added value: +{
+  "description": "Ship baggage: disembarkation date (Athens Art. 15 notice window + Art. 16 bar)",
+  "type": "string"
+}

changedInput schema / properties / disruption / description

Previous value: -"delay | cancellation | missed_connection | voyage_cancelled | missed_port | baggage_cabin | baggage_other | baggage_vehicle"New value: +"Disruption type (default delay)"

addedInput schema / properties / distance_km

Added value: +{
+  "description": "Coach: scheduled service distance (Reg 181/2011 applies from 250 km)",
+  "type": "string"
+}

addedInput schema / properties / express_surcharge

Added value: +{
+  "description": "Japan JR: limited-express surcharge paid (the refundable component)",
+  "type": "string"
+}

changedInput schema / properties / journey_date / description

Previous value: -"YYYY-MM-DD — claim-deadline math (UK 28 days, ferry 2 months, coach 3 months)"New value: +"YYYY-MM-DD — computes claim deadlines (UK 28 days, ferry 2 months, coach 3 months, JR 1 year)"

changedInput schema / properties / lang / description

Previous value: -"Response language code (en | es | fr | de | zh | hi | ar | pt | ja | ko | etc.)"New value: +"Letter language (default English)"

changedInput schema / properties / mode / description

Previous value: -"rail | coach | ferry | cruise"New value: +"Transport mode"

addedInput schema / properties / passenger_name

Added value: +{
+  "description": "Passenger name (placeholder if omitted)",
+  "type": "string"
+}

addedInput schema / properties / scheduled_journey_hours

Added value: +{
+  "description": "Ferry: scheduled crossing duration — selects the Art. 19 band",
+  "type": "string"
+}

addedInput schema / properties / scheme

Added value: +{
+  "description": "UK operator Delay Repay threshold (default DR30, conservative)",
+  "type": "string"
+}

addedInput schema / properties / service_number

Added value: +{
+  "description": "Train/sailing/coach identifier",
+  "type": "string"
+}

addedInput schema / properties / ticket_type

Added value: +{
+  "description": "UK Delay Repay percentages differ by ticket type",
+  "type": "string"
+}

addedInput schema / properties / travelled

Added value: +{
+  "description": "India TDR + FMC cruise refunds require you did NOT travel",
+  "type": "string"
+}

Changed9 schema fields changedJul 7, 2026

changedInput schema / properties / action / description

Previous value: -"Which endpoint to call. Options: status | city | route | commute | airport | agencies | delays | delays-history | trip | multimodal | compare | carfree | visitor | coverage"New value: +"Which endpoint to call. Options: status | city | route | commute | airport | agencies | delays | delays-history | trip | multimodal | compare | carfree | visitor | coverage | rights_check | rights_letter"

changedInput schema / properties / action / enum

Previous value: -[
-  "status",
-  "city",
-  "route",
-  "commute",
-  "airport",
-  "agencies",
-  "delays",
-  "delays-history",
-  "trip",
-  "multimodal",
-  "compare",
-  "carfree",
-  "visitor",
-  "coverage"
-]New value: +[
+  "status",
+  "city",
+  "route",
+  "commute",
+  "airport",
+  "agencies",
+  "delays",
+  "delays-history",
+  "trip",
+  "multimodal",
+  "compare",
+  "carfree",
+  "visitor",
+  "coverage",
+  "rights_check",
+  "rights_letter"
+]

addedInput schema / properties / country

Added value: +{
+  "description": "ISO country of the journey/scheme (GB, FR, US, CA, IN, JP, ... or EU)",
+  "type": "string"
+}

addedInput schema / properties / delay_minutes

Added value: +{
+  "description": "Arrival delay in minutes (rail/ferry); departure delay for coach",
+  "type": "string"
+}

addedInput schema / properties / disruption

Added value: +{
+  "description": "delay | cancellation | missed_connection | voyage_cancelled | missed_port | baggage_cabin | baggage_other | baggage_vehicle",
+  "type": "string"
+}

addedInput schema / properties / journey_date

Added value: +{
+  "description": "YYYY-MM-DD — claim-deadline math (UK 28 days, ferry 2 months, coach 3 months)",
+  "type": "string"
+}

addedInput schema / properties / mode

Added value: +{
+  "description": "rail | coach | ferry | cruise",
+  "type": "string"
+}

addedInput schema / properties / operator

Added value: +{
+  "description": "Operator/carrier name for the letter",
+  "type": "string"
+}

addedInput schema / properties / ticket_price

Added value: +{
+  "description": "Fare paid — percentage regimes compute the amount from this",
+  "type": "string"
+}

First observedJul 6, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations provided, the description carries the full behavioral-transparency burden. It discloses pricing, global coverage, and the deterministic/citation-locked nature of compensation letters, but omits authentication needs, rate limits, return format, and explicit read-only/mutation status—significant gaps for an API tool.

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?

The description is front-loaded with the core purpose and then structured as a clear endpoint list. It is somewhat long and contains redundancy (repeated 'TransitPulse') and dense regulatory detail, but the length is largely justified by the 16-endpoint scope and the need to convey the compensation engine's legal basis.

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?

The description covers the overall domain and endpoint selection well, but with 37 parameters and no output schema, it does not explain which parameters are relevant for each endpoint (e.g., which compensation fields are required for 'check' or 'letter') or what the return payloads look like. The schema covers parameter meanings, so the description is minimally adequate but leaves substantial gaps.

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 description coverage is 100%, so the baseline is 3. The description adds notable value for the required 'action' parameter by mapping each enum value to an endpoint behavior and price, which the schema does not do. Other parameters are already fully described in the schema, so no further compensation is needed.

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 clearly states the tool's role as 'global public transit intelligence' and a 'compensation recovery engine', with a specific verb and domain. It lists 16 endpoint actions with one-line descriptions, making the tool's scope and purpose immediately identifiable and distinguished from sibling 'pulse' tools.

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?

The endpoint list provides clear context for choosing among actions (status, delays, trip, letter, etc.) with pricing and brief semantics. It lacks explicit exclusion guidance or named alternatives, so it does not quite reach a 5, but the usage context is strong.

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

All pulsenetwork tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

transitpulse

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources