Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

scene_plan_presentation

Read-only

Propose measured overview and detail cameras with a capture profile, then check occlusion, lighting, and camera budget before previewing and recording the scene.

Instructions

Propose measured overview/detail cameras and a capture profile. regions use id,min,max, optional action/subject_ids. Review occlusion, lighting and existing camera budget; apply operations and preview before native recording.

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_id": "<scene_id>",
      "subject_ids": "<subject_ids>"
    },
    "name": "scene_plan_presentation"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNotechnical_showcase_1080p
regionsNo
scene_idYes
duration_sNo
azimuth_degNo
max_camerasNo
subject_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With readOnlyHint=true and openWorldHint=false already supplied, the description adds real context: it discloses that the planner checks occlusion, lighting and an existing camera budget, and that a preview precedes native recording, reinforcing its non-destructive nature. Against that, 'apply operations' is ambiguous and could be read as a state-changing action, which sits uneasily with the read-only annotation without being a direct contradiction.

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 compact sentences, front-loaded with the core capability and followed by input format then workflow caveats; nothing is padded. The telegraphic phrasing ('regions use id,min,max') is efficient but borders on cryptic for a reader without the surrounding schema.

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

Completeness2/5

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

This is a 7-parameter, 2-required tool with no parameter documentation, no output schema, and no enum values, yet the description covers only the regions layout and a loose workflow hint. An agent could not confidently choose a profile, set max_cameras, or interpret azimuth_deg from this text alone. Given the complexity, substantially more specification is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 7 parameters, so the description carries the full documentation burden. It only documents the shape of 'regions' (id, min, max, optional action/subject_ids), leaving profile, duration_s, azimuth_deg, max_cameras and subject_ids entirely unexplained beyond their bare names and defaults. One of seven parameters clarified is insufficient compensation.

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 opens with a specific verb and resource: 'Propose measured overview/detail cameras and a capture profile,' which tells an agent this is a camera-plan generator rather than an executor. It does not, however, differentiate itself from the many sibling planning tools (scene_plan_collision_audit, scene_plan_retime, scene_measure), so an agent cannot tell from the text alone which planner to reach for.

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?

'Review occlusion, lighting and existing camera budget; apply operations and preview before native recording' implies a workflow (plan → preview → record natively) but never states when to use this tool versus alternatives. Notably, occlusion review overlaps with the sibling scene_plan_collision_audit with no routing guidance. Usage is inferable from context but not explicitly directed.

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