Skip to main content
Glama
GongRzhe

Travel Planner MCP Server

optimize_itinerary

Refine travel plans by optimizing itineraries based on specific criteria such as time and cost, using the Travel Planner MCP Server for enhanced efficiency.

Instructions

Optimizes an existing itinerary based on specified criteria

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itineraryIdYesID of the itinerary to optimize
optimizationCriteriaYesCriteria for optimization (time, cost, etc.)

Implementation Reference

  • Handler for the 'optimize_itinerary' tool. Validates input using OptimizeItinerarySchema and returns a mock response with optimization details.
    case "optimize_itinerary": {
      const validatedArgs = OptimizeItinerarySchema.parse(args);
      return {
        content: [
          {
            type: "text",
            text: `Optimized itinerary ${validatedArgs.itineraryId} based on: ${validatedArgs.optimizationCriteria.join(", ")}`,
          },
        ],
      };
    }
  • Zod schema defining the input for the 'optimize_itinerary' tool: itineraryId (string) and optimizationCriteria (array of strings).
    const OptimizeItinerarySchema = z.object({
      itineraryId: z.string().describe("ID of the itinerary to optimize"),
      optimizationCriteria: z.array(z.string()).describe("Criteria for optimization (time, cost, etc.)"),
    });
  • index.ts:69-73 (registration)
    Registration of the 'optimize_itinerary' tool in the ListTools response, including name, description, and inputSchema.
    {
      name: "optimize_itinerary",
      description: "Optimizes an existing itinerary based on specified criteria",
      inputSchema: zodToJsonSchema(OptimizeItinerarySchema),
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it 'optimizes based on specified criteria' without disclosing behavioral traits like whether it modifies the original itinerary, requires specific permissions, has rate limits, or what the optimization entails (e.g., reordering, time adjustments). This leaves significant gaps for a mutation tool.

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 with zero waste, front-loaded with the core action. Every word earns its place, making it appropriately sized and structured.

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 as a mutation operation with no annotations and no output schema, the description is incomplete. It fails to explain what optimization does, what the return values are, or behavioral risks, leaving the agent with insufficient context for safe and effective use.

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 the schema already documents both parameters ('itineraryId' and 'optimizationCriteria'). The description adds no additional meaning beyond what the schema provides, such as examples of criteria or format details, meeting the baseline for high schema coverage.

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 action ('optimizes') and resource ('an existing itinerary'), specifying it works on existing itineraries rather than creating new ones. However, it doesn't differentiate from sibling tools like 'create_itinerary' or 'search_attractions' beyond the core function.

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 like 'create_itinerary' or 'search_attractions', nor does it mention prerequisites such as needing an existing itinerary ID. It lacks explicit when/when-not instructions or named alternatives.

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