Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

scene_compile_recipe

Read-only

Compile a versioned recipe into scene_apply operations at current base_revision using role bindings with asset_path and pinned asset_binding for atomic batch application, without scene edits/runs.

Instructions

Compile a versioned recipe into ordinary scene_apply operations at the current base_revision. Supply role bindings with asset_path and pinned asset_binding. This does not edit or run the scene and gives no physical pass; apply the full batch atomically, then freeze and verify a new trial.

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>",
      "recipe_id": "<recipe_id>",
      "parameters": "<parameters>",
      "bindings": "<bindings>"
    },
    "name": "scene_compile_recipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
bindingsYes
scene_idYes
recipe_idYes
parametersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with that by saying it 'does not edit or run the scene and gives no physical pass.' It adds useful operational context about operating at the current base_revision and about atomic application downstream, but it does not say what the returned compiled operations look like or how binding resolution 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 the core action and ending with the imperative next steps. Dense technical phrasing ('pinned asset_binding', 'gives no physical pass') costs some readability but nothing is wasted.

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 read-only compile step with no output schema this covers the action, its side-effect boundary, and the handoff to scene_apply. However, with zero schema documentation on four required parameters and nested objects, an agent still lacks enough to build a valid call in one pass.

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

Parameters1/5

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

Schema description coverage is 0% with four required parameters including two open nested objects. The description only partially illuminates the bindings object ('asset_path and pinned asset_binding') and says nothing about what 'parameters' should contain, how scene_id and recipe_id are interpreted, or why base_revision is not itself a parameter. It does not compensate for the documentation gap.

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?

The description gives a specific verb and resource ('Compile a versioned recipe into ordinary scene_apply operations') and explicitly names the sibling operation it expands into. An agent can tell this apart from scene_apply and the scene_plan_* family without opening the 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?

It states what to supply (role bindings with asset_path and a pinned asset_binding) and prescribes the follow-up workflow: apply the full batch atomically, then freeze and verify a new trial. What is missing is routing guidance against alternatives, e.g. when to compile a recipe rather than calling scene_apply directly or using scene_plan_* tools.

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