verse-mcp

Create a camera path (guided tour)

set_camera_path

Create guided walk or fly-through camera paths from 2–256 keyframes so a scene’s share link can play a custom tour; optionally promote a path as the default.

Instructions

Create a camera path: a guided walk or fly-through the share link can play. Give 2 to 256 keyframes, each with an eye position p, forward direction f and optional fov, dwell hold, ease, look-at target and chapter label. The first path becomes the scene's default; set make_default to promote later ones. If you only want a good default tour, use reset_auto_camera_path instead. 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>",
      "keys": "<keys>"
    },
    "name": "set_camera_path"
  }
}

Input Schema

Name	Required	Description	Default
`keys`	Yes
`mode`	No	'walk' keeps eye height over the floor and avoids walls; 'fly' goes anywhere.	walk
`name`	No		Walkthrough
`scene`	Yes	Scene id (e.g. palm-villa-0a1b2c3d4e5f), the job id returned by upload_scene, or a Verse share link.
`speed`	No	Metres per second for keys without `dur`.
`make_default`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 15, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent open-world write. The description adds genuinely new behavior: the first path silently becomes the scene default and later ones need make_default to be promoted, plus an owner/auth requirement. It does not mention what happens on repeated calls with the same name or how failures surface.

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?

Three tight sentences, front-loaded with purpose, then keyframe requirements, then default-path behavior and the alternative. No filler, though 'set make_default to promote later ones' is slightly compressed and requires reading the schema to parse fully.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter mutation tool with no output schema, the definition never says what the call returns (path id, name, URL), which matters because a follow-up list_camera_paths or create_share_link likely needs that identifier. The write-side semantics are well covered, but the return contract and per-parameter detail are left incomplete.

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 50%, and the description mostly restates keyframe fields (p, f, fov, hold, ease, label, look) that the schema already documents, including the 2-256 bound. It adds no meaning for mode, speed, name or dur, which are the parameters the schema leaves thin. Baseline 3 is appropriate; it does not compensate for the uncovered half.

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 ('Create a camera path') plus the domain concept it produces ('a guided walk or fly-through the share link can play'), which tells an agent what the artifact is for. It also names the sibling reset_auto_camera_path, so the tool is distinguishable without opening any 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?

Gives an explicit alternative with a selecting condition: 'If you only want a good default tour, use reset_auto_camera_path instead.' It also states a prerequisite ('Owner only; needs an account token'). What is missing is any guidance on when to use list_camera_paths to check existing paths before adding one.

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

Deploy Server