Skip to main content
Glama
Sign In

PrimeGuest

by io.primeguest.mcp
OverviewDiscussionsAdmin

Rooms, prices and cancellation for a hotel

check_availability
Read-onlyIdempotent

List every available room and rate at one hotel for given dates: total price, meals, cancellation terms and a link to book direct with the hotel. Takes a hotel_id.

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": {
      "hotel_id": "<hotel_id>",
      "check_in": "<check_in>",
      "check_out": "<check_out>"
    },
    "name": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomsNoNumber of rooms
adultsNoNumber of adults
check_inYesCheck-in date, YYYY-MM-DD
childrenNoNumber of children
hotel_idYesThe hotel_id shown with each hotel in search results
check_outYesCheck-out date, YYYY-MM-DD (after check-in)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / hotel_id / description
      Previous value: -"hotel_id from search_hotels"New value: +"The hotel_id shown with each hotel in search results"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so safety is covered. The description adds value by disclosing the payload contents (price, meals, cancellation terms, direct booking link), but says nothing about whether availability is live/cached, currency, or what happens when no rooms are available.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with a colon-delimited enumeration of return fields, so the agent gets purpose and payload in one pass. The trailing 'Takes a hotel_id' is mildly redundant with the schema but is a useful lead-in to the required parameter.

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?

With no output schema, the description usefully enumerates the returned fields, and all six inputs are documented in the schema. The main remaining gap is occupancy semantics (how rooms/adults/children interact) and failure behavior for unavailable dates.

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 all six parameters are already documented including date format, occupancy bounds and defaults. The description only restates hotel_id and the date-range intent, adding no semantics beyond the schema; baseline 3 applies.

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?

States a specific verb (list) and resource (available rooms and rates) scoped to one hotel, and enumerates what is returned: total price, meals, cancellation terms, booking link. This clearly distinguishes it from get_hotel and search_hotels, though it does not name those siblings explicitly.

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 only implied: 'Takes a hotel_id' plus the schema note that hotel_id comes from search results suggests the search-then-check flow, but the description never says when to prefer this over get_hotel or search_hotels, nor any exclusions such as minimum-stay or past-date constraints.

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

All PrimeGuest 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