Skip to main content
Glama
GongRzhe

Travel Planner MCP Server

get_transport_options

Retrieve available transportation options between specified origin and destination points for a given travel date using the Travel Planner MCP Server.

Instructions

Retrieves available transportation options between two points

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesTravel date (YYYY-MM-DD)
destinationYesDestination point
originYesStarting point

Implementation Reference

  • Handler for the 'get_transport_options' tool. Validates input using GetTransportOptionsSchema and returns a mock text response describing transport options between origin and destination on a given date.
    case "get_transport_options": {
      const validatedArgs = GetTransportOptionsSchema.parse(args);
      return {
        content: [
          {
            type: "text",
            text: `Transport options from ${validatedArgs.origin} to ${validatedArgs.destination}\n` +
                  `Date: ${validatedArgs.date}`,
          },
        ],
      };
    }
  • Zod schema defining the input parameters for the 'get_transport_options' tool: origin, destination, and date.
    const GetTransportOptionsSchema = z.object({
      origin: z.string().describe("Starting point"),
      destination: z.string().describe("Destination point"),
      date: z.string().describe("Travel date (YYYY-MM-DD)"),
    });
  • index.ts:79-83 (registration)
    Registration of the 'get_transport_options' tool in the listTools handler, including name, description, and input schema.
    {
      name: "get_transport_options",
      description: "Retrieves available transportation options between two points",
      inputSchema: zodToJsonSchema(GetTransportOptionsSchema),
    },
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. While 'retrieves' implies a read-only operation, the description doesn't mention important behavioral aspects like rate limits, authentication requirements, response format, whether results are cached, or what happens with invalid inputs. For a tool with zero annotation coverage, this is insufficient.

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 states the core purpose without any wasted words. It's appropriately sized for a straightforward retrieval tool and front-loads the essential information.

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?

For a simple retrieval tool with 100% schema coverage but no annotations and no output schema, the description is minimally adequate. It states what the tool does but lacks important context about behavioral characteristics, usage guidelines relative to siblings, and what the return value contains. The absence of output schema means the description should ideally hint at what's returned.

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 all three parameters with clear descriptions. The description adds no additional parameter semantics beyond what's in the schema - it mentions 'between two points' which corresponds to origin/destination parameters, but provides no extra context about format, constraints, or usage beyond the schema's descriptions.

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 tool's purpose with a specific verb ('retrieves') and resource ('available transportation options'), and specifies the scope ('between two points'). However, it doesn't differentiate this tool from potential sibling tools like 'optimize_itinerary' that might also involve transportation options.

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. With sibling tools like 'create_itinerary' and 'optimize_itinerary' that might involve transportation planning, there's no indication of when this specific retrieval tool is appropriate versus those more comprehensive tools.

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