Skip to main content
Glama

Search resorts

search_resorts
Read-onlyIdempotent

Search the Maldives accommodation catalog by name, atoll, star class, transfer mode, meal plan and experience. Results list resorts before guesthouses and are not a ranking by quality. Can also narrow to a short transfer from the airport or to stays with a 360° tour. Returns compact summaries.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_resorts"
  }
}

Input Schema

NameRequiredDescriptionDefault
atollNoAtoll name, partial match — e.g. "Baa", "South Ari".
limitNoMaximum results (1-60).
queryNoFree text: a name, island, atoll or words like honeymoon or overwater. Typo-tolerant for names.
mealPlanNoBoard basis — e.g. "All Inclusive", "Half Board".
starRatingNoOfficial star class.
experiencesNoProperties must match ALL of these: honeymoon, family, diving, snorkeling, surfing, wellness, adults-only, all-inclusive, overwater-villas, private-pool, manta-rays, whale-sharks, water-sports, house-reef, eco-friendly, luxury, budget-friendly.
propertyTypeNoRestrict to resorts or guesthouses.
transferTypeNoAirport transfer mode, partial match — e.g. "seaplane", "speedboat", "domestic".
hasVirtualTourNoTrue: only stays with a published 360° tour.
maxTransferMinutesNoOnly stays with a recorded airport transfer this short, in minutes. Uses the top of any range, adds up the legs of a two-part journey, and leaves out stays with no figure on record. Connection waits are not recorded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / hasVirtualTour
      Added value: +{
      +  "description": "True: only stays with a published 360° tour.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / maxTransferMinutes
      Added value: +{
      +  "description": "Only stays with a recorded airport transfer this short, in minutes. Uses the top of any range, adds up the legs of a two-part journey, and leaves out stays with no figure on record. Connection waits are not recorded.",
      +  "maximum": 240,
      +  "minimum": 5,
      +  "type": "integer"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for adding real context: results order resorts before guesthouses and are explicitly not a quality ranking, and it returns compact summaries rather than full records. It omits pagination/limit behavior, which is the only notable gap.

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?

Three tight sentences with no filler; the search scope and facet list come first, then the ordering caveat, then the optional narrowings. Slightly reorderable but no sentence is wasted.

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 10-parameter, zero-required search tool with no output schema, the description covers scope, ordering, and return shape ('compact summaries'), which is enough to invoke it correctly. Missing only edge-case behavior such as empty result handling or how the default limit applies.

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 every parameter is already documented, including the nuanced maxTransferMinutes semantics and the ALL-match rule for experiences. The description adds only a loose paraphrase of which facets exist and no format or syntax detail beyond the schema, so 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 ('Search') and resource ('Maldives accommodation catalog') and enumerates the facets it filters on (name, atoll, star class, transfer mode, meal plan, experience). It is clearly a catalog-wide search as opposed to the single-record siblings like get_resort or resolve_resort, though it never names a sibling 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?

It implies when to use it by describing the narrowing options ('Can also narrow to a short transfer from the airport or to stays with a 360° tour'), but gives no explicit when-not guidance or routing to alternatives such as compare_resorts, find_nearby, or similar_resorts.

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