Skip to main content
Glama

Find ready-made trip plans

search_trip_plans
Read-onlyIdempotent

Search Triptime AI's ready-made, day-by-day travel itineraries (520+ destinations worldwide) by city or country. Use this when the user asks for a trip plan or itinerary for a destination. Returns matching plans with the number of days, places and a link to open the plan on Triptime AI, plus a link to plan a custom trip.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "destination": "<destination>"
    },
    "name": "search_trip_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoPreferred trip length in days (optional).
languageNoLanguage for titles and links: the language the user writes in, when it is one of these (optional, default en).
destinationYesCity, region or country in English, e.g. "Rome", "Cappadocia", "Japan" (write "Lisbon", not "Lizbon").

Output Schema

NameRequiredDescriptionDefault
errorNo
plansNo
labelsNoDisplay labels for the trip card in the requested language.
plan_linkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorldHint=false, so safety is covered; the description adds useful context about what is returned (number of days, places, plan link, custom-trip link) and the breadth of the catalog. It does not state what happens when no plan matches the destination, which is the main remaining gap.

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?

Three tight sentences: what it is, when to use it, what comes back. The trigger condition is front-loaded and nothing is redundant.

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

Completeness4/5

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

For a read-only search with full schema coverage and an output schema, the description covers purpose, trigger and return summary. Only edge behavior (no matches, pagination/result limits) is unaddressed, which is minor here.

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%, so destination, days and language are already documented, and the schema even includes the English-spelling and enum guidance. The description only adds that search is 'by city or country', which slightly clarifies destination scope but contributes little beyond the schema.

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?

States a specific verb and resource ('Search ... ready-made, day-by-day travel itineraries') plus scope ('520+ destinations worldwide') and a distinguishing qualifier, 'ready-made', that separates it from the sibling tools that open or build a single/custom plan.

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 says 'Use this when the user asks for a trip plan or itinerary for a destination', which is a clear triggering condition. It stops short of an explicit when-not or naming get_trip_plan / plan_trip_link as alternatives, though the mention of a 'link to plan a custom trip' gestures at the alternative path.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources