Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

configure_modifier

Add, update, or remove SUBSURF, BEVEL, and SOLIDIFY modifiers on Blender objects with typed properties, approval checks, and stack validation.

Instructions

Typed add/update/remove for SUBSURF, BEVEL and SOLIDIFY modifiers. Requires trusted approval; verifies properties and stack. No apply/reorder or arbitrary RNA properties.

Input Schema

NameRequiredDescriptionDefault
nameYes
actionYes
task_idNo
approvedNoUntrusted caller flag; never proof of approval.
propertiesNo
modifier_nameYes
modifier_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does disclose real behavior: an approval gate, validation of properties and of the existing modifier stack, and hard scope limits. It stops short of describing failure modes, side effects on existing modifiers, or idempotency of add/update, which matter for a mutation tool with zero annotation coverage.

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

Conciseness5/5

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

Three short sentences, front-loaded with the verb and resource, then the approval requirement, then the exclusions. No filler and no repetition of schema content.

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 7-parameter mutation tool with nested conditional properties, no annotations and no output schema, the description covers scope and approval but leaves several parameters and the success/failure surface undocumented. It is adequate to decide whether to call the tool, less adequate to call it correctly.

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

Parameters2/5

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

Schema description coverage is only 14%, so the description must compensate and largely does not. 'Typed' hints that the properties object is constrained per modifier type (valuable, since the conditional schema is hard to parse), but task_id, the distinction between name and modifier_name, and the semantics of approved are never explained.

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

Purpose5/5

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

States a specific verb set (typed add/update/remove), a specific resource (SUBSURF, BEVEL and SOLIDIFY modifiers), and explicitly carves out what it is not (no apply/reorder). An agent can distinguish it from apply_modifier and edit_modifier_stack without opening either schema.

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

Usage Guidelines4/5

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

Gives clear negative guidance — no applying, no reordering, no arbitrary RNA properties — which routes the agent away from this tool toward siblings for those operations. It does not name the alternative tools or state the precondition for a successful call (how trusted approval is obtained), leaving some inference.

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