Skip to main content
Glama
full-aigc-plugins

partme_blender

by full-aigc-plugins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

rig.create_control

blender_rig_create_control

Create a rig control in Blender at a specified location with configurable shape and size. Use to add custom controls for rigging and animation.

Instructions

PartMe Blender Harness command rig.create_control. Risk: standard; maturity: L3. Requirements: Per-request argument checks and session policy still apply

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
sizeNo
shapeNo
locationYesThree finite numbers; rotation uses radians
_requestIdNoStable request id for replay safety
_authorizationNoAction-bound Harness authorization claim
_transactionIdYesHarness milestone transaction id
_expectedSceneRevisionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.5.3
    • removedInput schema / properties / shape / description
      Removed value: -"See command validation; detailed type not yet audited"
    • addedInput schema / properties / shape / enum
      Added value: +[
+  "CUBE",
+  "SPHERE",
+  "CIRCLE",
+  "ARROWS"
+]
    • addedInput schema / properties / shape / type
      Added value: +"string"
  2. First observedv0.1.0

TDQS

D1.5/5.0
Behavior2/5

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

Annotations are all false (not read-only, not idempotent, not destructive), but the description adds only risk and maturity labels plus a policy note. It does not disclose the operation's side effects, prerequisites, or what 'create control' actually does in the scene. There is no contradiction with annotations, but behavioral insight is minimal.

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

Conciseness2/5

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

The description is very short, but it is under-specification rather than concise efficiency. The two sentences convey no functional information and do not earn their place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 8 parametersaaaand an output schema, the description is almost empty. It gives no context about the operation's purpose, effects, prerequisites, return values, or place in the rigging workflow, leaving the agent to infer everything from the name and schema.

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 coverage is only 50%, with name, size, shape, and _expectedSceneRevision lacking descriptions in the schema. The description mentions none of the parameters and provides no meaning beyond the schema, so it fails to compensate for the undocumented half.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a restatement of the tool name: 'PartMe Blender Harness command `rig.create_control`.' It contains no verb, resource, or effect, and does not distinguish this from sibling rig tools like blender_rig_create_armature or blender_rig_bind.

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?

No statement about when to use this tool versus alternatives. The only guidance is a generic policy reminder ('Per-request argument checks and session policy still apply'), which addresses requirements rather than usage context or exclusion conditions.

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