Skip to main content
Glama

VakayMood

Get resort details

get_resort
Read-onlyIdempotent

Returns one resort: address, coordinates, amenities, unit types, policies, its page on vakaymood.com and its published questions and answers, which cover topics such as parking and its cost.

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": {
      "resort": "<resort>"
    },
    "name": "get_resort"
  }
}

Input Schema

NameRequiredDescriptionDefault
resortYesResort RR code (RR12345678), as returned in resort.id, or a resort slug from a previous result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful context beyond annotations by listing the returned fields, including the resort page and published Q&A topics. It does not describe not-found behavior, but for a simple read tool the behavioral disclosure is strong.

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?

The description is a single front-loaded sentence that states the return scope and then enumerates the relevant fields. Every clause contributes useful information, and there is no filler.

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 simple one-parameter read tool with rich annotations and no output schema, the description provides enough detail about what is returned. Missing error or not-found behavior is a minor gap that does not prevent correct invocation.

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 resort parameter is fully documented as an RR code or slug. The description itself adds no parameter semantics beyond the schema, so the baseline of 3 is appropriate.

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 one resort. It enumerates the returned content (address, coordinates, amenities, unit types, policies, page, Q&A), making the purpose clear. It does not explicitly distinguish itself from sibling tools such as get_listing or get_collection, but the resort resource is unambiguous.

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: retrieve detailed information for a single resort using its identifier. The description does not state when to prefer this tool over alternatives or when not to use it, so an agent must infer the context.

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