Skip to main content
Glama

VakayMood

Search available stays

search_availability
Read-onlyIdempotent

Searches publicly visible timeshare rental stays on vakaymood.com by place, resort, date window, sleeping capacity, nightly price and brand. Returns stays with fixed dates, itemized pricing in USD and the vakaymood.com URL where each stay is booked. All parameters are optional and combinable. Each result is a summary: the bed configuration, kitchen equipment, cancellation terms, VakayFlex option, notices, unit amenities and unit policies of a stay are returned by get_listing for its listingId, and the policies and published questions and answers of its resort by get_resort for its resort.id.

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_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number.
sortNoResult ordering. start_asc (default) orders by check-in date, then nightly price.
brandNoResort brand.
limitNoResults per page. Default 10.
resortNoOne resort, given as an RR code (RR12345678) or a resort slug from a previous result.
sleepsNoMinimum sleeping capacity.
checkinNoStart of the search window, YYYY-MM-DD.
checkoutNoEnd of the search window, YYYY-MM-DD.
locationNoFree-form place name, matched against resort country, state and city. Example: Orlando Florida.
max_nightly_priceNoUpper bound on the nightly rate in USD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. Beyond that the description adds real context: results are 'summaries' only, pricing is itemized in USD with fixed dates, each result carries a booking URL, and 'publicly visible' scopes the inventory. It does not say anything about result volumes or pagination behavior beyond the schema.

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 purpose, then return shape, then escalation path to sibling tools. Sentence three enumerates many detail fields (bed configuration, kitchen equipment, cancellation terms, VakayFlex, notices, amenities, policies) which is slightly heavy but serves as precise routing to get_listing/get_resort.

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 10 optional params and no output schema, the description carries the return-value burden and does so by describing the summary shape and where deferred details live. Pagination defaults, sorting options and price bounds are all left to the fully documented schema, which is reasonable; only cross-tool scope versus collections is unaddressed.

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 baseline is 3. The description adds meaning the schema does not state: filters are combined (AND semantics) rather than alternatives, and checkin/checkout are framed as a search window rather than exact stay dates — a non-obvious semantic for date filters.

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 ('searches') and resource ('publicly visible timeshare rental stays on vakaymood.com') plus the full filter surface: place, resort, date window, sleeping capacity, nightly price, brand. It also distinguishes itself from siblings by naming get_listing and get_resort as the tools for detail fields it does not return.

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?

Clear about what the tool is for and explicitly notes all filters are optional and combinable, so an agent knows a zero-argument call is valid. It routes to get_listing (by listingId) and get_resort (by resort.id) for details. It does not contrast with get_collection/list_collections, so the sibling boundary is only partially drawn.

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