Skip to main content
Glama

VakayMood

Get listing details

get_listing
Read-onlyIdempotent

Returns the full detail of one publicly visible stay: unit type, bed configuration, fixed check-in and check-out dates, itemized pricing in USD, standard cancellation terms, the optional VakayFlex cancellation upgrade with its fee and guaranteed refund, notices such as a parking charge or renovation work, unit amenities such as kitchen equipment, unit policies, resort amenities and the vakaymood.com URL where it is booked. A stay that is no longer publicly visible is reported as not found.

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": {
      "listing_id": "<listing_id>"
    },
    "name": "get_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
listing_idYesListing VK code (VK04437967), as returned in listingId, or a listing slug from a bookingUrl.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description's genuine additions are content-level: visibility scoping (only publicly visible stays), the not-found outcome, USD pricing, and the presence of notices and an optional upgrade. That is useful, but it is data-content disclosure rather than behavioral disclosure such as rate limits, permissions, or staleness of availability data, so it sits at a solid middle score against already-rich 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?

It is front-loaded with the verb and resource, and every clause maps to a distinct category of returned data, so nothing is padding. The trade-off is that all of this is packed into one very long sentence with chained "such as" examples, which is denser and harder to scan than a short lead sentence plus a structured list would be.

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 carries the burden of describing return content, and it does so thoroughly by category, plus it documents the not-found behavior for listings that lost visibility. For a single-parameter read-only lookup whose annotations cover the safety profile, nothing an agent needs in order to call it correctly is missing.

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% and the single listing_id parameter is already documented with both the VK code format and the slug alternative, so the description correctly does not repeat it. It adds nothing about the parameter beyond the schema, which is the baseline-3 case for full coverage.

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?

The description states a specific verb and resource ("Returns the full detail of one publicly visible stay") and enumerates exactly what that detail contains, from bed configuration to cancellation terms and the booking URL. It never names a sibling tool or explicitly contrasts itself with search_availability or get_resort, so the differentiation is inferred rather than stated.

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 implied rather than prescribed: "one ... stay" signals a single-record lookup rather than a search, and the not-found clause implies it should be called only for listings believed to be live. There is no explicit when-to-use guidance, no prerequisite or alternative-tool routing, and no note about what to do when the caller only has a name rather than an ID.

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