partme_blender

by full-aigc-plugins

Overview Schema Source Related Servers Discussions Admin

Python

Local

render.configure

blender_render_configure

Configure Blender render settings such as engine, resolution, samples, and device to prepare a scene for rendering.

Instructions

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

Input Schema

TableJSON Schema

Name	Required	Description
`look`	No
`width`	No
`device`	No
`engine`	Yes
`height`	No
`samples`	No
`exposure`	No
`_requestId`	No	Stable request id for replay safety
`transparent`	No
`_authorization`	No	Action-bound Harness authorization claim
`_transactionId`	Yes	Harness milestone transaction id
`allowCpuFallback`	No
`_expectedSceneRevision`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.5.3Sep 22, 2026
- removedInput schema / properties / engine / description
```
Removed value: -"See command validation; detailed type not yet audited"
```
- addedInput schema / properties / engine / enum
```
Added value: +[
+  "AUTO",
+  "BLENDER_EEVEE_NEXT",
+  "BLENDER_EEVEE",
+  "CYCLES"
+]
```
- addedInput schema / properties / engine / type
```
Added value: +"string"
```
First observedv0.1.0Sep 15, 2026

TDQS

D1.6/5.0

Behavior2/5

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

Annotations are all false and do not convey safety or side-effect information, so the description carries the disclosure burden. It adds 'Risk: standard; maturity: L3' and a note about argument checks, but does not disclose that this is a mutation operation, what state it changes, whether it triggers a re-render, or how the harness session is affected.

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 brief, but brevity here is under-specification rather than conciseness. It front-loads no useful functional information, and every clause is generic harness boilerplate rather than content that helps an agent invoke the tool.

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?

This is a complex tool with 13 parameters and a low-coverage schema, yet the description provides no functional context whatsoever. Even though an output schema exists and return-value documentation is not required, the description fails to explain the tool's purpose, when to use it, or what the parameters configure.

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 description coverage is only 23% across 13 parameters, and the description does not explain any parameter's meaning or purpose. It does not compensate for the low schema coverage and offers zero semantic guidance for engine, device, samples, exposure, or the transaction-related parameters.

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

Purpose2/5

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

The description only restates the command name `render.configure` and adds generic harness metadata (risk, maturity, requirements). It never states what the tool actually does—whether it configures the render engine, output resolution, or scene settings—so an agent cannot understand its function from the description alone.

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?

There is no guidance on when to use this tool versus alternatives such as blender_render_configure_passes or blender_render_inspect. The phrase 'Requirements: Per-request argument checks and session policy still apply' is a policy note, not a usage guideline, and provides no decision context.

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

Deploy Server