Skip to main content
Glama

VakayMood

Get collection details

get_collection
Read-onlyIdempotent

Returns one published collection: its editorial as sanitized HTML, published questions and answers, member resorts with their vakaymood.com pages and starting nightly prices, and its lowest priced available stays in ascending price order.

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": {
      "slug": "<slug>"
    },
    "name": "get_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesCollection slug, as returned by list_collections.
limitNoNumber of lowest priced stays to return. Default 10.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the description's job is mostly to characterise the read. It adds real value beyond that by disclosing the exact payload composition, that the editorial is sanitized HTML, and that the stay list is sorted ascending by price.

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?

One sentence, front-loaded with what is returned, then the payload items in a compact list. Every clause carries information, though the single long enumeration is harder to scan than a short bulleted structure would be.

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?

There is no output schema, so the description must carry return semantics, and it does so thoroughly for a two-parameter read tool. The remaining gap is edge behaviour: what is returned or raised for a nonexistent or unpublished slug, and whether all members are returned irrespective of limit.

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?

With 100% schema description coverage, the schema already documents both slug and limit, so the baseline is 3. The description adds only marginal semantics, chiefly that the price ordering applies to the limited list, so limit truncates an ascending-price sequence rather than an arbitrary one.

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 verb and resource are explicit ('Returns one published collection') and the payload is enumerated: editorial HTML, Q&A, member resorts with pages and starting nightly prices, and lowest priced stays. That is specific enough to separate it from list_collections, but no sibling is named, so it stays a notch below a fully differentiating statement.

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 only implied: the reader infers 'call this to fetch details for a single collection' from the singular return and the 'published' qualifier. There is no explicit when-to-use vs get_resort/get_listing, and no statement of what to do when a slug is unpublished or unknown.

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