Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

configure_material_shader

Writes typed Principled Base Color, Metallic, Roughness, and IOR values and adds, updates, or removes one Noise.Color node in a Base Color graph, rejecting conflicting links.

Instructions

Typed Principled Base Color/Metallic/Roughness/IOR writes and add/update/remove of one Noise.Color to Base Color graph. Exact sockets only; conflicting links rejected. Requires trusted approval and separate readback.

Input Schema

NameRequiredDescriptionDefault
actionYes
inputsNo
task_idNo
approvedNoUntrusted flag, never approval proof.
target_nameYes
noise_inputsNo
bsdf_node_nameYes
noise_node_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does substantial work: it discloses typed writes, exact-socket matching, rejection of conflicting links, a trusted-approval requirement, and that results are not returned (separate readback needed). It still omits atomicity/partial-failure behavior and what happens to pre-existing links, keeping it below 5.

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

Conciseness4/5

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

Three tight sentences, front-loaded with the data payload and ending with the approval/readback constraint. The compressed first clause ('Typed Principled Base Color/Metallic/Roughness/IOR writes') is dense to the point of being hard to parse, but nothing is wasted.

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

Completeness3/5

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

For a tool with a heavily conditional 8-parameter schema, nested objects, no annotations and no output schema, the description covers the mutation scope, rejection behavior and approval requirement adequately. It leaves gaps around the node-name/task_id parameters and the noise parameter set, which an agent would have to guess from the raw schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 13% (only 'approved' is documented), so the description must compensate. It does explain the semantics of the `inputs` group (the four named Principled sockets) and that a single noise node is being added/updated/removed, but target_name, bsdf_node_name, noise_node_name, task_id and the noise_inputs fields (scale/detail/distortion) get no meaning added beyond the schema.

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

Purpose4/5

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

The description names a concrete verb ('writes') and concrete resources ('Principled Base Color/Metallic/Roughness/IOR' and 'one Noise.Color to Base Color graph'), and the compound scope (set_principled vs. add/update/remove noise) is stated. It implicitly separates itself from inspect_/read tools via 'separate readback', but never names a sibling explicitly, so it stops short of a 5.

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

Usage Guidelines3/5

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

'Requires trusted approval and separate readback' gives real preconditions, and 'conflicting links rejected' implies a failure case. However, there is no statement of when to prefer this over inspect_material_shader or connect_shader_nodes, and no explicit when-not guidance; usage must be inferred from the scope sentence.

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