Skip to main content
Glama

GetMyHotels

by com.getmyhotels

Search

search
Read-only

Search GetMyHotels for hotels matching a query. Returns a list of results with ids that can be passed to fetch for full details. Provide the destination and travel dates in the query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesNatural-language search, e.g. 'hotels in Lisbon 2026-08-10 to 2026-08-14 for 2 adults'.
roomsNoRooms (1-6). Default 1.
adultsNoAdults (1-10). Default 2.
checkInNoCheck-in date, ISO 8601 (YYYY-MM-DD).
checkOutNoCheck-out date, ISO 8601 (YYYY-MM-DD). Must be after check-in.
childrenNoChildren (0-6). Default 0.
keywordsNoOptional free-text preferences, e.g. 'beachfront pool spa'.
destinationNoCity, region, or place to search (e.g. 'Paris', 'Goa', 'Lower Manhattan').
childrenAgesNoAge of each child at check-in. Length should equal `children`.
guestNationalityNoISO 3166-1 alpha-2 guest nationality (e.g. 'US', 'GB'). Affects supplier pricing.

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already mark it as read-only and open-world. The description adds that it returns a list of results with IDs for fetching full details, which is useful. No contradictory behavior is mentioned.

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 that efficiently state purpose, result format, and a usage hint. Every sentence serves a purpose with no wasted words.

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?

Given 10 parameters and no output schema, the description covers overall purpose but lacks detail on handling complex queries or edge cases. It mentions 'fetch' for details but doesn't clarify when to use other sibling tools.

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?

With 100% schema description coverage, the schema already documents all parameters. The description provides high-level guidance (e.g., include dates in query), adding marginal value over the schema.

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 searches for hotels and returns IDs for fetching details. However, it does not distinguish itself from the sibling 'search_hotels', which likely has similar functionality.

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?

The description advises providing destination and travel dates in the query, but lacks explicit guidance on when to use this tool versus alternatives like 'search_hotels'. No when-not or exclusion criteria are given.

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

All GetMyHotels toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool targets a distinct action or resource, e.g., search vs search_hotels, get_booking vs get_my_booking. No overlapping functionality; descriptions clarify subtle differences.

Naming Consistency4/5

Most tools follow verb_noun pattern (add_trip_item, cancel_booking) or get_/list_ prefixes. One outlier ('fetch') breaks the pattern slightly, but overall naming is predictable.

Tool Count5/5

18 tools cover the hotel booking domain comprehensively without being excessive. Each tool has a clear role in the workflow from search to booking to modification.

Completeness5/5

Covers all key lifecycle stages: search, details, rooms, pricing, checkout (standard and one-click), booking management (list, get, cancel, modify), payment methods, and trip saving. No obvious gaps.

Resources