Skip to main content
Glama

travelpulse

Retrieve real-time travel intelligence: park waits, hours, crowds, weather, deals, itinerary, visa, insurance, packing, budget, currency, phrasebook, and translation. Global coverage for trip planning.

Instructions

TravelPulse: Global travel intelligence API. AI-synthesized destination guides, visa requirements, currency exchange, health advisories, packing lists, phrasebooks, weather, and travel insurance. Integrates real-t

Coverage: Global

Endpoints: • waits ($0.10): Live park wait times • hours ($0.10): Park hours and schedule • crowds ($0.10): Crowd prediction • weather ($0.10): Travel weather forecast • deals ($0.10): Travel deals • plan ($0.10): Trip itinerary • visa ($0.10): Visa requirements by nationality and destination • insurance ($0.10): 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.10): Currency exchange rates and money tips for destination • phrasebook ($0.10): Essential travel phrasebook by destination language • translate ($0.10): Real-time travel translation (menus, signs, conversations)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesWhich endpoint to call. Options: waits | hours | crowds | weather | deals | plan | visa | insurance | pack | budget | currency | phrasebook | translate
langNolang
parkNoPark name or slug e.g. magic-kingdom, universal-studios-florida, europa-park
dateNoYYYY-MM-DD, default today
destinationNodestination
daysNodays
styleNostyle
budgetNobudget
nationalityNoPassport nationality (e.g. US, UK, India, Brazil, Nigeria)
purposeNoVisit purpose (tourism, business, nomad, transit)
trip_typeNoTrip type — determines coverage priorities
duration_daysNoTrip duration in days
trip_cost_usdNoTotal prepaid trip cost in USD — for cancellation coverage sizing
durationNoTrip duration in days
activitiesNoPlanned activities (e.g. hiking, beach, business, diving, winter sports)
bag_typeNoLuggage constraint
fromNoHome currency (e.g. USD, EUR, GBP) — default: USD
toNoDestination currency or country name
amountNoAmount to convert for reference calculation
focusNoPhrase focus area (transport, food, emergency, shopping, all)
textNoText to translate
from_langNoSource language (auto-detected if omitted)
to_langNoTarget language (default: English)
contextNoContext hint (menu, sign, conversation, product)
Behavior2/5

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

No annotations are present, so the description carries full responsibility. It mentions 'AI-synthesized' and 'Integrates real-t' (likely real-time) but lacks details on data freshness, rate limits, authentication, or side effects. Behavioral traits are poorly disclosed.

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 well-structured with a clear opening and a bulleted list of endpoints. Though the endpoint list is somewhat verbose, it is organized and front-loaded with the core purpose.

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

Completeness2/5

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

Given the tool's complexity (24 parameters, many endpoints, no output schema), the description is incomplete. It fails to explain return formats across endpoints or how parameters interact, leaving significant gaps.

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%, and the description does not add meaning beyond the parameter names and brief schema descriptions. Baseline of 3 is appropriate; no extra value provided.

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 identifies TravelPulse as a global travel intelligence API with a comprehensive list of specific endpoints (waits, hours, crowds, etc.). The title and content distinguish it from sibling tools, none of which are travel-focused.

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 is provided on when to use this tool versus alternatives. The description lists endpoints but does not offer usage context, prerequisites, or exclusions. The agent is left to infer appropriate use cases.

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