Skip to main content
Glama
Sign In

hotels

by com.fostay
OverviewDiscussionsAdmin

Search hotels in Dubai, Abu Dhabi or Goa (Fostay)

search_stays
Read-only

Search hotels in Dubai, Abu Dhabi or Goa. For Dubai and Abu Dhabi, returns Fostay's hand-curated edit first (8 flagship stays with editorial verdicts), then catalog matches (~2,000 bookable hotels). For Goa, returns the best-reviewed hotels and resorts (hostels and homestays only when searched by name), optionally narrowed to one area. Use get_live_rates for prices. Results include a fostay_url where a human can view photos, live rates and book.

Input Schema

NameRequiredDescriptionDefault
areaNoGoa only: narrow to one area — candolim-calangute-baga (Candolim, Calangute & Baga); anjuna-vagator (Anjuna, Vagator & Assagao); morjim-mandrem-arambol (Morjim, Mandrem, Arambol & Siolim); panaji-old-goa (Panaji & Old Goa); south-goa-beaches (Colva, Benaulim, Varca & Cavelossim); palolem-agonda (Palolem & Agonda)
cityYesCity or destination to search
limitNoMax catalog results (default 10)
queryNoOptional hotel-name filter, e.g. 'Atlantis' or 'Rove'
min_ratingNoMinimum guest rating on a 10 scale, e.g. 8

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / area
      Added value: +{
+  "description": "Goa only: narrow to one area — candolim-calangute-baga (Candolim, Calangute & Baga); anjuna-vagator (Anjuna, Vagator & Assagao); morjim-mandrem-arambol (Morjim, Mandrem, Arambol & Siolim); panaji-old-goa (Panaji & Old Goa); south-goa-beaches (Colva, Benaulim, Varca & Cavelossim); palolem-agonda (Palolem & Agonda)",
+  "enum": [
+    "candolim-calangute-baga",
+    "anjuna-vagator",
+    "morjim-mandrem-arambol",
+    "panaji-old-goa",
+    "south-goa-beaches",
+    "palolem-agonda"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / city / description
      Previous value: -"City to search"New value: +"City or destination to search"
    • changedInput schema / properties / city / enum
      Previous value: -[
-  "Dubai",
-  "Abu Dhabi"
-]New value: +[
+  "Dubai",
+  "Abu Dhabi",
+  "Goa"
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds substantial behavior beyond that: curated edit returned first for Dubai/Abu Dhabi, ~2,000 catalog matches, Goa's review-based ordering, hostels/homestays surfacing only on name search, and inclusion of a fostay_url for human follow-up.

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 with the primary action and scope, then the branch-specific behavior. Every sentence carries distinct information; the three-city breakdown is dense but each clause is load-bearing.

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 carries return-value burden and does so by describing the result composition (curated edit vs catalog) and the fostay_url. Pagination/limit behavior and the min_rating filter's effect are left to the schema, which is acceptable at full coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. However the description adds meaning beyond the schema by disclosing that the query parameter changes result composition (hostels/homestays only when searched by name) and that area optionally narrows Goa results.

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) plus resource (hotels/stays) and bounded scope (Dubai, Abu Dhabi, Goa), then differentiates itself from siblings by routing price lookups to get_live_rates. An agent can distinguish this from booking_status, demand_calendar or prepare_booking without opening any 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?

Explicitly names get_live_rates as the alternative for prices, which is concrete routing. It also explains per-city result behavior, but does not state outright when not to use this tool (e.g. for booking or availability) or any prerequisites.

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

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