verse-mcp

Plan the automatic tour

reset_auto_camera_path

Idempotent

Re-plan a scene's automatic camera path for interiors, exteriors, or products and set it as the default, returning a link that autoplays the new walkthrough or orbit.

Instructions

Re-plan the scene's automatic camera path (an eye-height walkthrough for interiors, a drone fly-through for exteriors, a 360 orbit for products) and make it the default. Returns a link that autoplays it. Owner only; needs an account token.

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": {
      "scene": "<scene>"
    },
    "name": "reset_auto_camera_path"
  }
}

Input Schema

Name	Required	Description	Default
`scene`	Yes	Scene id (e.g. palm-villa-0a1b2c3d4e5f), the job id returned by upload_scene, or a Verse share link.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 15, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare non-read-only, open-world, idempotent, non-destructive, so the description's job is to add what those don't cover: the change persists as the default, it returns a link that autoplays, and it requires owner permission plus an account token. That is meaningful context beyond the structured fields, though it does not say what happens to a previously existing path.

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 front-loaded sentence: action first, the mode distinctions in a compact parenthetical, then the return behavior and access requirement. Every clause carries information; no filler or repetition.

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 one-parameter mutation with no output schema, it covers the action, the resulting default state, what comes back (an autoplaying link), and the auth model. Minor gaps remain around failure/overwrite behavior for an existing path.

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?

Single required parameter with 100% schema description coverage that already explains the accepted id, job-id, or share-link formats. The description adds no further parameter meaning, which is acceptable at 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?

Specific verb+resource: re-plans the scene's automatic camera path and makes it default, with the three content modes (interior walkthrough, exterior fly-through, product orbit) spelled out. It does not explicitly contrast with the sibling set_camera_path, so an agent must infer that this tool regenerates rather than assigns an existing path.

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?

The description implies the use case (you want a freshly generated tour set as the default) and states a hard prerequisite (owner only, account token). It never says when not to use it or names set_camera_path/list_camera_paths as alternatives, leaving the comparison to inference from the tool names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server