Skip to main content
Glama
GongRzhe

Travel Planner MCP Server

get_accommodations

Search for accommodation options in a specific location by providing check-in and check-out dates and an optional budget. Simplify travel planning with accurate lodging results.

Instructions

Searches for accommodation options in a specified location

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
budgetNoMaximum price per night
checkInYesCheck-in date (YYYY-MM-DD)
checkOutYesCheck-out date (YYYY-MM-DD)
locationYesLocation to search

Implementation Reference

  • Handler function for get_accommodations tool that validates input using the schema and returns a mock formatted text response with accommodation details.
    case "get_accommodations": {
      const validatedArgs = GetAccommodationsSchema.parse(args);
      return {
        content: [
          {
            type: "text",
            text: `Accommodation options in ${validatedArgs.location}\n` +
                  `Dates: ${validatedArgs.checkIn} to ${validatedArgs.checkOut}\n` +
                  `Budget: ${validatedArgs.budget || "Not specified"} per night`,
          },
        ],
      };
    }
  • Zod schema defining the input parameters for the get_accommodations tool: location, check-in date, check-out date, and optional budget.
    const GetAccommodationsSchema = z.object({
      location: z.string().describe("Location to search"),
      checkIn: z.string().describe("Check-in date (YYYY-MM-DD)"),
      checkOut: z.string().describe("Check-out date (YYYY-MM-DD)"),
      budget: z.number().optional().describe("Maximum price per night"),
    });
  • index.ts:84-88 (registration)
    Registers the get_accommodations tool in the ListTools response, including name, description, and input schema.
    {
      name: "get_accommodations",
      description: "Searches for accommodation options in a specified location",
      inputSchema: zodToJsonSchema(GetAccommodationsSchema),
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions searching but doesn't disclose behavioral traits such as whether results are paginated, if authentication is required, rate limits, or what the output format looks like. For a search tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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 appropriately sized and front-loaded, making it easy to understand at a glance.

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 (a search operation with 4 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns, how results are structured, or any behavioral constraints, leaving the agent with insufficient information for 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?

The description adds minimal meaning beyond the input schema, which has 100% coverage with clear descriptions for all parameters. It implies location-based searching but doesn't provide additional context like search radius or result limits. With high schema coverage, the baseline score of 3 is appropriate as the schema does most of the work.

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 ('searches') and resource ('accommodation options'), and specifies the scope ('in a specified location'). It doesn't explicitly distinguish from sibling tools like 'create_itinerary' or 'search_attractions', but the focus on accommodations is clear enough for basic differentiation.

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 or exclusions. It merely states what the tool does without context for selection among available options.

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