Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

create_cyclorama

Creates a parameterized curved studio sweep backdrop with tangent-continuous cove geometry, enabling product staging and visualization with predictable dimensions.

Instructions

Creates a parameterized seamless curved studio sweep backdrop (infinite cove) with smooth shading, tangent continuity, and predictable bounding dimensions for product staging and visualization.

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": {
      "name": "<name>"
    },
    "name": "create_cyclorama"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the cyclorama object to create.StudioCyclorama
depthNoFloor depth along Y axis in meters.
widthNoWidth along X axis in meters.
task_idNo
approvedNo
locationNo
request_idNo
cove_radiusNoFillet radius of the curved transition cove.
wall_heightNoHeight of the back wall along Z axis in meters.
cove_segmentsNoSubdivision segments along the cove curve.
approval_tokenNo
rotation_eulerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it delivers mostly geometric adjectives (smooth shading, tangent continuity, predictable bounds) rather than operational behavior. Critically, the schema contains task_id, approved, request_id, and approval_token, implying an approval-gated workflow, yet the description never mentions gating, permissions, or whether the created object is added to the active scene. Nothing is said about failure modes or the response.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no filler, which is efficient, but it is a dense run of technical adjectives that conveys no structure for a 12-parameter tool. The size is fine; the organization leaves nothing scannable for the agent to act on.

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 mutation tool with 12 parameters, no annotations, no output schema, and only 50% schema coverage, the description is thin. The approval-workflow parameters and the placement parameters are entirely unaddressed, so an agent cannot confidently determine preconditions for a successful call from this definition alone.

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 only 50%, so the description needs to compensate, and it does not. It gestures at cove_radius and cove_segments via 'curved transition' and 'parameterized' but never names or clarifies them, and the six undocumented workflow parameters (task_id, approved, request_id, approval_token, location, rotation_euler) get no explanation of their role or interaction with the creation call.

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?

States a specific verb (creates) and a specific, well-defined resource: a seamless curved studio sweep backdrop / infinite cove. The parenthetical gloss and the listed geometric properties make the output object unambiguous. It does not differentiate itself from adjacent siblings such as create_primitive, create_room_enclosure, or create_building_envelope, so it stops short of a 5.

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 only implied through the trailing phrase 'for product staging and visualization', which gives a domain context but no explicit when-to-use or when-not-to-use rule. There is no mention of choosing this over create_primitive or create_room_enclosure for a studio backdrop, and no prerequisites are stated. Adequate but inference is required.

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