Render a Material Maker node's output to a PNG image at a specified path, with configurable width, height, and output channel. Ensure the destination directory exists first.
Render one node output to a PNG file; the destination directory must exist.
| Name | Required | Description | Default |
|---|---|---|---|
| node | Yes | ||
| path | Yes | ||
| width | No | ||
| height | No | ||
| output | No | ||
| material_id | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.3.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false, so the agent knows this is a destructive write operation. The description adds a useful prerequisite that the destination directory must exist, but it does not disclose whether an existing PNG is overwritten or what permissions are required.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single compact sentence that front-loads the action and includes the key operational constraint. There is no filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Although an output schema exists and annotations cover safety, the tool has six parameters with zero schema descriptions and the description does little to fill that gap. For a destructive file-writing tool, it should do more to clarify parameter meanings and usage relative to siblings.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% across six parameters, so the description must compensate. It only vaguely implies the 'node' and 'path' parameters and says nothing about width, height, output, or material_id, leaving most parameters semantically undocumented.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: render one node output to a PNG file. It is clear on its own, but it does not explicitly differentiate itself from sibling tools like render_material_variations or preview_material, which also produce visual outputs.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides only a prerequisite (destination directory must exist) but no guidance on when to use this tool versus siblings such as preview_material, save_material_preview, or render_material_variations. There is no indication of when it is not appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.