Skip to main content
Glama
Sign In
prompt-to-scene

prompt-to-scene

by 316sandon12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_interactive_prop

Build a door, chest, or pickup with Blender geometry and native gameplay behavior, outputting separate base and moving meshes plus a reusable Unity prefab or UE Blueprint.

Instructions

Build a door, chest or pickup with Blender geometry and native gameplay behavior.

Dimensions are width/depth/height in meters; position uses target engine axes. Retains separate base/moving meshes and a reusable Unity prefab or UE Blueprint. Poll this workflow until completed. Aim the game camera and press E for the optional demo, or bind your own input.

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": {
      "kind": "<kind>",
      "asset_id": "<asset_id>"
    },
    "name": "create_interactive_prop"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
colorNo
asset_idYes
positionNo
dimensionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningfully: it discloses an asynchronous 'workflow' that must be polled until completed, retained base/moving mesh structure, Unity prefab / UE Blueprint output, and an optional demo requiring camera aim plus E. It omits permission/asset-overwrite behavior, but the async and artifact-model disclosure is substantial.

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?

Front-loads the core capability, then units/axes, then artifact retention, then the async polling contract. Dense but structured; the closing demo/input-binding sentence is the least essential and could be trimmed.

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 5-param mutation with no annotations and no output schema, the description covers units, axis convention, async polling, retained meshes, and the target engine artifact. The main gap is asset_id semantics (does it create or overwrite a library asset?), but overall it is sufficient to invoke the tool.

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 coverage is 0%, so the description must compensate: it defines dimensions as width/depth/height in meters, explains that position uses target engine axes, and implies the valid 'kind' values (door/chest/pickup). However, color and asset_id remain undocumented in both schema and text, so the compensation is partial.

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 ('Build a door, chest or pickup') and pins the differentiator: 'native gameplay behavior', which separates it from plain prop siblings like create_prop, revise_prop, and edit_prop_part. An agent can choose this tool without opening a schema.

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?

Usage is implied by the phrase 'interactive prop' and the demo instructions, but the description never says when to prefer this over create_prop, create_prop_set, or configure_interaction, nor when it is inappropriate. Adequate but leaves routing to inference.

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

Deploy Server

Other Tools