Skip to main content
Glama

Airsockfly

Search hotels

search_hotels
Read-onlyIdempotent

Search hotels in a city or area for given check-in and check-out dates. Returns offers with the total price of the stay, rating, board type and a link to the offer page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "place": "<place>",
      "checkIn": "<checkIn>",
      "checkOut": "<checkOut>"
    },
    "name": "search_hotels"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of offers to return, from 1 to 30. Default 10.
placeYesCity or area where the hotel should be.
roomsNoNumber of rooms.
adultsNoNumber of adults.
checkInYesCheck-in date, YYYY-MM-DD.
checkOutYesCheck-out date, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds value beyond them by disclosing the return payload — total stay price, rating, board type, and a link to the offer page — which matters since no output schema exists. It stops short of noting result caps or pricing variability across occupancy, keeping it below a 5.

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?

Two sentences, zero filler: the action and scope come first, then the return contents. Every clause carries information an agent cannot get elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter search tool with full schema coverage and no output schema, the description supplies the essentials: what it searches, what dates drive it, and what comes back. Minor gaps remain around occupancy effects on pricing and result limits, but nothing needed to invoke it correctly is missing.

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%, including formats and min/max bounds, so the schema carries parameter meaning. The description only reinforces that place is a city/area and that dates drive the search; it adds nothing about how rooms/adults affect offers or what board type covers. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (search) and resource (hotels) plus the scoping inputs (city/area, check-in/check-out dates). The resource noun alone distinguishes it from siblings like search_cars and search_flights without needing to open the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the description ('for given check-in and check-out dates'), which signals it is a date-bound availability search rather than an offer detail lookup. However, it gives no explicit when-to-use vs alternatives guidance (e.g., versus get_offer once an offer link is returned) and no prerequisites or exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources