Skip to main content
Glama

generate_3d_scene

Apply deterministic CSS perspective rotation to product screens for MotionForge timelines, enabling consistent angled visuals without building mesh or Three.js scenes.

Instructions

Apply deterministic CSS perspective rotation to a product screen. No mesh/Three.js scene generation.

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": {
      "timeline": "<timeline>",
      "shotIndex": "<shotIndex>",
      "output": "<output>"
    },
    "name": "generate_3d_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
outputYes
timelineYes
shotIndexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the agent knows this writes something but is not destructive. The description adds a genuinely useful trait not in the annotations — that the transform is deterministic — and clarifies the rendering approach is CSS-based rather than 3D mesh work. It does not say what is written, where the output lands, or how it interacts with the timeline/shot artifacts, so it beats the annotation baseline only modestly.

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?

Two short, front-loaded sentences with the core mechanism stated first and the disambiguation second; no filler. The brevity is only slightly self-defeating because the saved space is not spent on the missing parameter or usage guidance.

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?

An output schema exists, so return values need no explanation, but everything else is thin: three required arguments are entirely undocumented, there is no routing guidance among the ~30 siblings, and the write side effects of a non-readOnly tool are unstated. For a mutation tool with zero schema coverage, the description does too little.

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 three required parameters (timeline, shotIndex, output), so the description carries full responsibility for explaining them and says nothing. It never clarifies what 'timeline' refers to, that shotIndex is bounded to 0-29, or that 'output' is a file path versus an identifier — the agent must guess at every argument.

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 names a specific verb and mechanism ('Apply deterministic CSS perspective rotation') plus a concrete target ('a product screen'), which is far more informative than the tool name alone. It also pre-empts confusion with a negative scope statement ('No mesh/Three.js scene generation'), though it does not distinguish itself from likely siblings such as create_camera_movement or animate_product_interface.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is an exclusion ('No mesh/Three.js scene generation'), which tells the agent what this tool is not but never states when to choose it over the many sibling scene/animation tools. There is no positive trigger condition, no prerequisite, and no named alternative to route to.

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