Skip to main content
Glama
Sign In

OKstays

by com.okstays
OverviewDiscussionsAdmin

Compare hotels

compare_hotels
Read-onlyIdempotent

Use this when the user is choosing between 2-4 specific hotels. Returns each hotel's Comfort Score breakdown, price, strengths and complaints, the signals where they differ most, and a verdict: best comfort, cheapest, best value. Hotel ids come from search_hotels (hotel_name finds a hotel the user names). Read-only, no sign-in.

Input Schema

NameRequiredDescriptionDefault
adultsNoGuests per room (1-8), if given.
checkinNoUser's check-in date, YYYY-MM-DD (e.g. 2027-03-12), if given: links then open on this stay.
checkoutNoCheck-out date, YYYY-MM-DD (e.g. 2027-03-15).
hotel_idsYes2-4 hotel ids from search_hotels.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / adults / description
      Previous value: -"Guests per room, if given."New value: +"Guests per room (1-8), if given."
    • changedInput schema / properties / checkin / description
      Previous value: -"User's check-in date, YYYY-MM-DD, if given: links then open on this stay."New value: +"User's check-in date, YYYY-MM-DD (e.g. 2027-03-12), if given: links then open on this stay."
    • changedInput schema / properties / checkout / description
      Previous value: -"Check-out date, YYYY-MM-DD."New value: +"Check-out date, YYYY-MM-DD (e.g. 2027-03-15)."
  2. Changed3 schema fields changed
    • addedInput schema / properties / adults
      Added value: +{
+  "description": "Guests per room, if given.",
+  "maximum": 8,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / checkin
      Added value: +{
+  "description": "User's check-in date, YYYY-MM-DD, if given: links then open on this stay.",
+  "type": "string"
+}
    • addedInput schema / properties / checkout
      Added value: +{
+  "description": "Check-out date, YYYY-MM-DD.",
+  "type": "string"
+}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already carry read-only/idempotent/no-sign-in semantics, yet the description still adds real value by enumerating what comes back: Comfort Score breakdown, price, strengths/complaints, differing signals, and a verdict. It doesn't cover ordering, ties, or latency, but the output shape disclosure is the useful part beyond annotations.

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?

Front-loaded trigger sentence followed by a dense but well-ordered enumeration of returns. Slightly packed—the parenthetical about hotel_name is easy to miss—but no sentence is filler.

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

Completeness5/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 assumes responsibility for describing return content and does so, while annotations handle the safety profile and the required id source is explained. An agent has everything needed to call it and interpret the result.

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 coverage is 100%, so the schema already documents all four parameters including ranges and date format. The description only adds the provenance of hotel_ids (from search_hotels) and a note that a hotel name can locate a named hotel; that is useful but minimal, so 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 (compare) and resource (2-4 specific hotels) and immediately differentiates from siblings by naming search_hotels as the id source, implicitly separating it from single-hotel get_hotel and find_similar_hotels. An agent can select it without opening 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 Guidelines4/5

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

"Use this when the user is choosing between 2-4 specific hotels" gives a clear trigger, and it explains where the ids come from. It stops short of stating the inverse case (a single hotel → get_hotel, or open-ended browsing → search_hotels), so the routing is good but not exhaustive.

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

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