Skip to main content
Glama
GongRzhe

Travel Planner MCP Server

create_itinerary

Generate personalized travel itineraries by inputting origin, destination, dates, budget, and preferences to plan trips efficiently.

Instructions

Creates a personalized travel itinerary based on user preferences

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
budgetNoBudget in USD
destinationYesDestination location
endDateYesEnd date (YYYY-MM-DD)
originYesStarting location
preferencesNoTravel preferences
startDateYesStart date (YYYY-MM-DD)

Implementation Reference

  • index.ts:97-110 (handler)
    Handler for the create_itinerary tool: validates input using CreateItinerarySchema and returns a mock text response with itinerary details.
    case "create_itinerary": {
      const validatedArgs = CreateItinerarySchema.parse(args);
      return {
        content: [
          {
            type: "text",
            text: `Created itinerary from ${validatedArgs.origin} to ${validatedArgs.destination}\n` +
                  `Dates: ${validatedArgs.startDate} to ${validatedArgs.endDate}\n` +
                  `Budget: ${validatedArgs.budget || "Not specified"}\n` +
                  `Preferences: ${validatedArgs.preferences?.join(", ") || "None specified"}`,
          },
        ],
      };
    }
  • Zod schema defining the input structure for the create_itinerary tool.
    const CreateItinerarySchema = z.object({
      origin: z.string().describe("Starting location"),
      destination: z.string().describe("Destination location"),
      startDate: z.string().describe("Start date (YYYY-MM-DD)"),
      endDate: z.string().describe("End date (YYYY-MM-DD)"),
      budget: z.number().optional().describe("Budget in USD"),
      preferences: z.array(z.string()).optional().describe("Travel preferences"),
    });
  • index.ts:64-68 (registration)
    Registration of the create_itinerary tool in the ListTools response, including name, description, and input schema.
    {
      name: "create_itinerary",
      description: "Creates a personalized travel itinerary based on user preferences",
      inputSchema: zodToJsonSchema(CreateItinerarySchema),
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'creates' implying a write operation, but doesn't mention permissions, side effects, rate limits, or what the output looks like (e.g., format, success indicators). This is inadequate for a mutation tool with zero annotation coverage.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and appropriately sized, making it easy for an agent to parse quickly.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain the return values, error conditions, or behavioral traits like idempotency or data persistence. Given the complexity of creating a personalized itinerary, more context is needed to guide the agent effectively.

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?

The description adds no parameter-specific information beyond what's in the schema, which has 100% coverage with clear descriptions for all 6 parameters. The baseline score of 3 is appropriate as the schema does the heavy lifting, but the description doesn't enhance understanding of how parameters interact or affect the itinerary creation.

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?

The description clearly states the verb ('creates') and resource ('personalized travel itinerary'), specifying it's based on user preferences. However, it doesn't differentiate from sibling tools like 'optimize_itinerary' which might also create or modify itineraries, so it's not fully distinctive.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'optimize_itinerary' or other siblings. It mentions 'based on user preferences' but doesn't specify prerequisites, exclusions, or comparative contexts, leaving the agent with minimal usage direction.

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

Related 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/GongRzhe/TRAVEL-PLANNER-MCP-Server'

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