pulsenetwork

travelpulse

TravelPulse: Global travel intelligence API for AI agents: weather, hotel deals, theme-park wait times, translation, trip plans, visas, health, currency, insurance, points. Any destination + language. x402 USDC (Base + Solana); no accounts, no keys.

Coverage: Global

Endpoints: • waits ($0.05): Live park wait times • hours ($0.05): Park hours and schedule • crowds ($0.08): Crowd prediction • weather ($0.15): Travel weather forecast • deals ($0.08): Travel deals • plan ($0.20): Trip itinerary • visa ($0.08): Visa requirements by nationality and destination • insurance ($0.08): Travel insurance comparison and recommendation • pack ($0.10): AI packing list by destination, climate, and activities • budget ($0.10): Daily travel budget by destination and style • currency ($0.08): Currency exchange rates and money tips for destination • phrasebook ($0.05): Essential travel phrasebook by destination language • translate ($0.03): Real-time travel translation (menus, signs, conversations) • health ($0.08): Destination health advisories and vaccine requirements • fare-intel ($0.12): Flight fare intelligence — when to book, cheapest months • points ($0.12): Points & miles redemption optimizer • trip-check ($0.50): One-call pre-booking trip clearance (visa + health + safety + weather + money) • disruption ($0.25): Flight disruption risk for an airport and date • check ($0.05): Flight compensation eligibility — EU261 / UK261 / Canada APPR / Brazil ANAC 400 / Turkey SHY / India DGCA (deterministic) • letter ($2.00): Citation-backed flight compensation claim letter (6 regimes, ready to send)

Input Schema

TableJSON Schema

Name	Required	Description
`to`	No	Destination currency or country name
`date`	No	YYYY-MM-DD, default today
`days`	No	days
`from`	No	Home currency (e.g. USD, EUR, GBP) — default: USD
`goal`	No	Redemption goal, e.g. 'business class to Japan' or 'free hotel week in Europe'
`lang`	No	lang
`park`	No	Park name or slug e.g. magic-kingdom, universal-studios-florida, europa-park
`text`	No	Text to translate
`cabin`	No	economy \| premium_economy \| business \| first
`dates`	No	Travel window, free-form (e.g. 2026-09-10 to 2026-09-20)
`focus`	No	Phrase focus area (transport, food, emergency, shopping, all)
`route`	No	Route, e.g. 'LHR-JFK' or 'London to Tokyo'
`style`	No	style
`action`	Yes	Which endpoint to call. Options: waits \| hours \| crowds \| weather \| deals \| plan \| visa \| insurance \| pack \| budget \| currency \| phrasebook \| translate \| health \| fare-intel \| points \| trip-check \| disruption \| check \| letter
`amount`	No	Amount to convert for reference calculation
`budget`	No	budget
`reason`	No	Cause per the carrier (default unknown — burden of proof is the carrier's)
`region`	No	Country/region the user holds cards/programs in
`airline`	No	Airline name for the letter
`airport`	No	Airport IATA code or city (e.g. JFK, Heathrow, Frankfurt)
`context`	No	Context hint (menu, sign, conversation, product)
`purpose`	No	Visit purpose (tourism, business, nomad, transit)
`to_lang`	No	Target language (default: English)
`bag_type`	No	Luggage constraint
`duration`	No	Trip duration in days
`passport`	No	Passport nationality (e.g. US, UK, India, Brazil, Nigeria). `nationality` accepted as an alias.
`programs`	No	Comma-separated list of programs/cards the user holds
`from_lang`	No	Source language (auto-detected if omitted)
`trip_type`	No	Trip type — determines coverage priorities
`activities`	No	Planned activities (e.g. hiking, beach, business, diving, winter sports)
`disruption`	No	delay \| cancellation \| denied_boarding \| baggage_delay \| baggage_damage \| baggage_loss (default delay)
`claim_value`	No	Baggage claims: documented damages with currency (e.g. '480 USD') — demanded in the letter, capped by the Montreal limit
`delay_hours`	No	Arrival delay at final destination in hours (e.g. 4.5)
`destination`	No	destination
`distance_km`	No	Great-circle distance override for airports outside the reference table
`flexibility`	No	exact \| ±3days \| month
`flight_date`	No	Flight date YYYY-MM-DD
`nationality`	No	Traveler nationality — some vaccines required only for specific nationals
`notice_days`	No	Cancellations: days of advance notice
`carrier_size`	No	Canada APPR carrier size (default large)
`duration_days`	No	Trip duration in days
`flight_number`	No	Flight number (e.g. LH400)
`trip_cost_usd`	No	Total prepaid trip cost in USD — for cancellation coverage sizing
`trip_duration`	No	Trip duration (affects prophylaxis recommendations)
`month_or_dates`	No	Target month or dates
`passenger_name`	No	Passenger name (placeholder used if omitted)
`carrier_country`	No	Operating carrier home country ISO code, or EU (default EU)
`block_time_hours`	No	India DGCA cancellations: scheduled block time in hours (estimated from distance if omitted, labeled [ESTIMATE])
`bag_received_date`	No	Baggage claims: date the bag was returned/received (YYYY-MM-DD) — computes the Art. 31 complaint deadline

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedJul 7, 2026

addedInput schema / properties / bag_received_date

Added value: +{
+  "description": "Baggage claims: date the bag was returned/received (YYYY-MM-DD) — computes the Art. 31 complaint deadline",
+  "type": "string"
+}

addedInput schema / properties / claim_value

Added value: +{
+  "description": "Baggage claims: documented damages with currency (e.g. '480 USD') — demanded in the letter, capped by the Montreal limit",
+  "type": "string"
+}

changedInput schema / properties / disruption / description

Previous value: -"Disruption type (default delay)"New value: +"delay | cancellation | denied_boarding | baggage_delay | baggage_damage | baggage_loss (default delay)"

Changed18 schema fields changedJul 7, 2026

changedInput schema / properties / action / description

Previous value: -"Which endpoint to call. Options: waits | hours | crowds | weather | deals | plan | visa | insurance | pack | budget | currency | phrasebook | translate | health | fare-intel | points"New value: +"Which endpoint to call. Options: waits | hours | crowds | weather | deals | plan | visa | insurance | pack | budget | currency | phrasebook | translate | health | fare-intel | points | trip-check | disruption | check | letter"

changedInput schema / properties / action / enum

Previous value: -[
-  "waits",
-  "hours",
-  "crowds",
-  "weather",
-  "deals",
-  "plan",
-  "visa",
-  "insurance",
-  "pack",
-  "budget",
-  "currency",
-  "phrasebook",
-  "translate",
-  "health",
-  "fare-intel",
-  "points"
-]New value: +[
+  "waits",
+  "hours",
+  "crowds",
+  "weather",
+  "deals",
+  "plan",
+  "visa",
+  "insurance",
+  "pack",
+  "budget",
+  "currency",
+  "phrasebook",
+  "translate",
+  "health",
+  "fare-intel",
+  "points",
+  "trip-check",
+  "disruption",
+  "check",
+  "letter"
+]

addedInput schema / properties / airline

Added value: +{
+  "description": "Airline name for the letter",
+  "type": "string"
+}

addedInput schema / properties / airport

Added value: +{
+  "description": "Airport IATA code or city (e.g. JFK, Heathrow, Frankfurt)",
+  "type": "string"
+}

addedInput schema / properties / block_time_hours

Added value: +{
+  "description": "India DGCA cancellations: scheduled block time in hours (estimated from distance if omitted, labeled [ESTIMATE])",
+  "type": "string"
+}

addedInput schema / properties / carrier_country

Added value: +{
+  "description": "Operating carrier home country ISO code, or EU (default EU)",
+  "type": "string"
+}

addedInput schema / properties / carrier_size

Added value: +{
+  "description": "Canada APPR carrier size (default large)",
+  "type": "string"
+}

addedInput schema / properties / dates

Added value: +{
+  "description": "Travel window, free-form (e.g. 2026-09-10 to 2026-09-20)",
+  "type": "string"
+}

addedInput schema / properties / delay_hours

Added value: +{
+  "description": "Arrival delay at final destination in hours (e.g. 4.5)",
+  "type": "string"
+}

addedInput schema / properties / disruption

Added value: +{
+  "description": "Disruption type (default delay)",
+  "type": "string"
+}

addedInput schema / properties / distance_km

Added value: +{
+  "description": "Great-circle distance override for airports outside the reference table",
+  "type": "string"
+}

addedInput schema / properties / flight_date

Added value: +{
+  "description": "Flight date YYYY-MM-DD",
+  "type": "string"
+}

addedInput schema / properties / flight_number

Added value: +{
+  "description": "Flight number (e.g. LH400)",
+  "type": "string"
+}

changedInput schema / properties / nationality / description

Previous value: -"Passport nationality (e.g. US, UK, India, Brazil, Nigeria)"New value: +"Traveler nationality — some vaccines required only for specific nationals"

addedInput schema / properties / notice_days

Added value: +{
+  "description": "Cancellations: days of advance notice",
+  "type": "string"
+}

addedInput schema / properties / passenger_name

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

addedInput schema / properties / passport

Added value: +{
+  "description": "Passport nationality (e.g. US, UK, India, Brazil, Nigeria). `nationality` accepted as an alias.",
+  "type": "string"
+}

addedInput schema / properties / reason

Added value: +{
+  "description": "Cause per the carrier (default unknown — burden of proof is the carrier's)",
+  "type": "string"
+}

First observedJul 6, 2026

TDQS

A3.7/5.0

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 reveals useful behavioral traits: per-call pricing for every endpoint, payment via 'x402 USDC (Base + Solana)', 'no accounts, no keys', and 'deterministic' for the check endpoint. However, it does not explicitly state read-only nature, output format, rate limits, or side effects, leaving transparency incomplete.

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?

The description is well-structured and front-loaded: a compact intro, coverage line, and an alphabetized bullet list that combines endpoint name, price, and purpose in one line each. Every sentence and bullet adds value with no filler or redundant elaboration.

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 49 parameters, 20 actions, and no output schema, the description gives a strong overview but lacks per-endpoint parameter requirements and output details. For example, it does not clarify which parameters apply to the 'check' or 'letter' actions versus 'visa' or 'health', leaving an agent to infer parameter-action relationships.

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%, but many parameter descriptions are tautological ('days', 'style', 'destination', 'budget'). The description adds meaning by explaining endpoint purposes (e.g., 'visa: Visa requirements by nationality and destination'), which hints at relevant parameters, but it does not map specific parameters to each of the 20 actions, a serious gap given 49 parameters.

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 'Global travel intelligence API for AI agents' and enumerates 20 distinct endpoints with specific purposes such as 'Live park wait times', 'Trip itinerary', and 'Flight compensation eligibility'. This is a specific verb+resource framing that distinguishes it from travel-related siblings and makes the tool's function obvious.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The endpoint list implies when to use each sub-function (e.g., 'visa: Visa requirements by nationality and destination'), but there is no explicit guidance about when to prefer this tool over alternatives, which sibling tool to use instead, or exclusions. Usage guidance is purely implicit through endpoint descriptions.

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.

travelpulse

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources