Skip to main content
Glama

VakayMood

List curated collections

list_collections
Read-onlyIdempotent

Returns every published VakayMood collection: a curated group of resorts (a destination, a brand, a price cap or a season) with its current starting nightly price in USD and its page on vakaymood.com. The slug of each collection identifies it in get_collection.

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": "list_collections"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds meaningful scope detail beyond that: only published collections are returned (drafts excluded), and each entry carries a live USD starting nightly price and a vakaymood.com page. It is silent on ordering and result size, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action and scope, followed by the one piece of routing information an agent needs. No filler, and the parenthetical definition of a collection earns its space by preventing a misread of the resource.

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 must carry the return-value burden and largely does: published-only scope, per-collection price and page URL, and a slug field for follow-up lookups. What is missing is the response shape (array wrapper, field names, ordering), which is modest but real for a tool with no output schema.

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?

The tool takes zero parameters, so the baseline is 4; the description correctly implies no filtering or paging inputs are needed to get the complete set. There is no input to add meaning to, and it does not misrepresent the absence of inputs.

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 and resource ('Returns every published VakayMood collection') and then defines what a collection actually is (a curated group of resorts by destination, brand, price cap or season) plus what each record carries. The final sentence ties the result to the sibling tool get_collection via the slug, so an agent can tell list vs. detail apart without opening either 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?

The 'every published' phrasing makes clear this is the unfiltered enumeration endpoint with no narrowing options, and the slug sentence tells the agent this is the entry point before calling get_collection. There is no explicit statement of when not to use it (e.g., searching availability), so it falls short of full when/when-not guidance.

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