Skip to main content
Glama
full-aigc-plugins

partme_blender

by full-aigc-plugins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

compositor.add_tracking_mask

blender_compositor_add_tracking_mask

Adds a tracking mask to Blender's compositor using motion tracking data, enabling mask-based compositing from tracked clip points.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clipYes
pointsYes
maskNameYes
_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. Changed1 schema field changedv0.2.0
    • addedInput schema / properties / points / items
      Added value: +{
+  "description": "Three finite numbers; rotation uses radians",
+  "items": {
+    "type": "number"
+  },
+  "maxItems": 3,
+  "minItems": 3,
+  "type": "array"
+}
  2. First observedv0.1.0

TDQS

D1.1/5.0
Behavior1/5

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

Annotations are all false (readOnly, openWorld, idempotent, destructive), but the description adds no behavioral context. It mentions 'Risk: standard; maturity: L3' which are not behavioral traits. The description does not disclose side effects, required permissions, or any operational implications. It adds nothing beyond the annotations.

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 this is under-specification rather than conciseness. It lacks any structural elements like a purpose statement or usage examples. The single sentence does not convey actionable information, so it is not a case of efficient brevity but rather a failure to specify.

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?

Given the tool's complexity (7 parameters, no obvious output schema details in description) and the absence of any functional explanation, the description is completely inadequate. An agent cannot determine what 'add_tracking_mask' does, what inputs are needed beyond the schema, or what the expected result is. Even with an output schema present, the core action remains undefined.

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 43% (3 of 7 parameters have descriptions in the schema). The description does not mention any parameter, so it fails to compensate for the low coverage. Parameters like `clip`, `maskName`, and `_expectedSceneRevision` have no explanation anywhere, and the description provides no additional meaning.

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 does not state what the tool does. It only identifies it as a 'PartMe Blender Harness command' with the name `compositor.add_tracking_mask`, which is essentially restating the title. There is no verb, resource, or behavior described, making it a tautology and failing to distinguish it from any other Blender command.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool or which alternatives might be more appropriate. The description mentions 'Per-request argument checks and session policy' but these are generic operational notes, not usage context. There is no mention of typical scenarios, prerequisites, or exclusion criteria.

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