Skip to main content
Glama

Get a 360° tour's scene list

get_vr_tour
Read-onlyIdempotent

The scene graph for one published 360° tour: every panorama with its title, category and panorama image URLs: what a guest can walk through before booking.

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

Input Schema

NameRequiredDescriptionDefault
slugYesResort slug (not the tour key) — e.g. "w-maldives".
categoryNoFilter scenes to one category, e.g. "Villas & Suites", "Dining".

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 cover read-only, idempotent, non-destructive, and closed-world behavior. The description adds meaningful context beyond that: only published tours are covered and the return contents are panoramas with title, category, and image URLs.

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?

A single front-loaded sentence with no wasted wording. It communicates scope and return shape efficiently.

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 still explains the return contents well enough: every panorama with title, category, and image URLs. Combined with annotations and a fully described input schema, an agent has what it needs to call the tool correctly.

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%, so the schema already explains that slug is a resort slug, not a tour key, and that category filters scenes. The description does not add further parameter meaning beyond noting that category is an attribute of each panorama.

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 resource and scope: the scene graph for one published 360° tour, listing every panorama with its title, category, and image URLs. The singular 'one published' distinguishes it from the sibling list_vr_tours, which lists all tours.

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?

Provides a clear usage context: viewing what a guest can walk through before booking. It implies this is for a single tour, but does not explicitly name alternatives or exclusion conditions such as unpublished tours.

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