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

prompt-to-scene

by 316sandon12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

configure_interaction

Attach/update door/chest/pickup behavior. Pivot/offset are local engine XYZ meters.

Instructions

Attach/update door/chest/pickup behavior. Pivot/offset are local engine XYZ meters.

A door/chest requires a separate prepared moving asset. The first UE attachment converts the plain managed StaticMeshActor to a native Blueprint; later revisions keep that Actor.

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

Input Schema

NameRequiredDescriptionDefault
kindYes
usesNo
angleNo
labelNo
pivotNo
asset_idYes
distanceNo
event_idNo
demo_inputNo
moving_offsetNo
moving_asset_idNo
depleted_asset_idNo
interaction_pointNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.13.0
    • addedInput schema / properties / depleted_asset_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Depleted Asset Id"
+}
    • addedInput schema / properties / event_id
      Added value: +{
+  "default": "",
+  "title": "Event Id",
+  "type": "string"
+}
    • addedInput schema / properties / interaction_point
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Interaction Point"
+}
    • addedInput schema / properties / label
      Added value: +{
+  "default": "",
+  "title": "Label",
+  "type": "string"
+}
    • addedInput schema / properties / uses
      Added value: +{
+  "default": 3,
+  "title": "Uses",
+  "type": "integer"
+}
  2. Addedv0.7.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose genuinely useful behavior beyond the schema: pivot/offset are in local engine XYZ meters, and the first attachment mutates the managed StaticMeshActor into a native Blueprint while later revisions preserve that Actor. It still omits permissions, reversibility, error modes, and what happens for non-door/chest kinds.

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 short sentences, front-loaded with the action, then the unit caveat, then the stateful-attachment note. The telegraphic style is dense but every sentence carries information; no filler.

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?

For a 13-parameter mutation tool with no annotations, no output schema, and 0% schema coverage, the description is far too thin. It communicates the moving-asset prerequisite and the one-time Blueprint conversion, but an agent still cannot correctly populate the majority of parameters from this text.

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 13 parameters. The description only clarifies the units/space of pivot and moving_offset; kind's allowed values, and the meaning of uses, angle, distance, event_id, demo_input, moving_asset_id, depleted_asset_id, and interaction_point are undocumented anywhere.

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 pair plus resource: 'Attach/update door/chest/pickup behavior', so an agent knows it configures interactive behavior on an existing asset. It does not, however, distinguish itself from close siblings like create_interactive_prop or edit_prop_part, so sibling routing is left to inference.

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?

It gives one real usage constraint: doors/chests require a separately prepared moving asset before this will work. There is no when-to-use vs when-not guidance, no statement about which kinds are valid, and no pointer to an alternative tool for creating rather than configuring interactions.

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