Skip to main content
Glama

MolTravel

by com.moltravel
OverviewDiscussionsAdmin

skiplagged_sk_hotels_search

[skiplagged] Search Skiplagged for hotels in a city with specific check-in and check-out dates, including ratings and pricing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityYesCity name to search for hotels (will be matched against available cities)
sortNoSort hotels by price (cheapest first), ranking (highest rated first), value (best value rating), or discount (best deals first, default when deals available)value
limitNoMaximum number of hotels to return (default: 12, max: 100)
offsetNoNumber of hotels to skip for pagination (default: 0)
checkinYesCheck-in date (YYYY-MM-DD format)
checkoutYesCheck-out date (YYYY-MM-DD format)
numRoomsNoNumber of rooms (default: 1, max: 9)
numAdultsNoNumber of adults (default: 2, max: 10)
numChildrenNoNumber of children (default: 0, max: 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / properties / checkin / pattern
      Removed value: -"^\\d{4}-\\d{2}-\\d{2}$"
    • addedInput schema / properties / checkout / $ref
      Added value: +"#/properties/checkin"
    • removedInput schema / properties / checkout / pattern
      Removed value: -"^\\d{4}-\\d{2}-\\d{2}$"
    • removedInput schema / properties / checkout / type
      Removed value: -"string"
    • addedInput schema / properties / city / minLength
      Added value: +1
    • addedInput schema / properties / offset / maximum
      Added value: +99
    • removedInput schema / properties / renderMode
      Removed value: -{
-  "description": "Preferred render mode for tool output (ui or text).",
-  "enum": [
-    "ui",
-    "text"
-  ],
-  "type": "string"
-}
  2. Added
  3. Removed
  4. Added

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It does convey that the action is a search and states the broad response includes ratings and pricing. However, it does not disclose pagination behavior, city-matching limitations, or other operational constraints that are part of the parameter schema.

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 clear sentence that front-loads the tool's purpose, action, and result. No redundant or unnecessary wording is present.

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?

The description is adequate for a straightforward hotel search tool, especially since the schema covers all parameters richly. However, there is no output schema, and the description doesn't mention pagination, sorting, room/guest options, or how city matching works, so it is not fully self-contained for an agent.

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 itself already documents each parameter. The description adds only a high-level mention of city and dates, but does not provide additional meanings beyond what the input schema already states. Baseline of 3 is appropriate.

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 ('Search Skiplagged for hotels in a city') and includes the key parameters (check-in and check-out dates), plus the output context (ratings and pricing). It is more specific than a mere restatement of the tool name, though it does not explicitly differentiate itself from the sibling skiplagged_sk_hotel_details tool.

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?

No usage guidance is provided. The description does not say when to prefer this search over hotel_details, flights_search, or other accommodation search tools, nor does it mention any prerequisites or exclusions. The intended use is only implied by the word 'search'.

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

All MolTravel toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources