partme_blender

Overview Schema Source Related Servers Discussions Admin

scene.set_units

blender_scene_set_units

Set Blender scene units to metric, imperial, or none, and adjust scale length for accurate measurements across the project.

Instructions

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

Input Schema

TableJSON Schema

Name	Required	Description
`system`	Yes
`_requestId`	No	Stable request id for replay safety
`scaleLength`	No
`_authorization`	No	Action-bound Harness authorization claim
`_transactionId`	Yes	Harness milestone transaction id
`_expectedSceneRevision`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 15, 2026

TDQS

D1.1/5.0

Behavior1/5

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

The description only mentions risk and maturity levels, which are not behavioral traits. Annotations already indicate it is not read-only, idempotent, or destructive, but the description adds no context about side effects, reversibility, or interaction with the scene. It fails to disclose what happens when units are set.

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?

While the description is short, it is under-specified rather than concise. It lacks substance and structure, providing no useful information beyond the title.

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 6 parameters and an output schema, this description is woefully incomplete. It does not explain what the tool does, when to use it, or how parameters behave, making it impossible for an agent to call it correctly without external knowledge.

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?

The description does not mention any parameters, and schema coverage is only 50%. The schema describes some internal fields but not the key ones like 'system' or 'scaleLength'. The description adds no meaning to these parameters, leaving their purpose and valid values unexplained.

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 simply restates the tool name as 'PartMe Blender Harness command `scene.set_units`' without explaining what setting units entails. It offers no verb, resource, or outcome beyond the title, making it a tautology.

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 versus alternatives like blender_scene_inspect or other scene-related tools. The description does not mention any conditions, prerequisites, or exclusions.

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

Deploy Server