Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

configure_curve_geometry

Create or update Blender curves and text with explicit splines, control points, and bevel/extrusion settings, or copy a curve to a mesh while preserving the source object.

Instructions

Finite atomic curve/text create/update or evaluated copy_to_mesh. Explicit Bezier/poly/NURBS splines/control points, text body/settings, bevel/extrusion. Update requires current snapshot; converted copy preserves source. Finite contract verified in disposable Blender 5.2.2; not arbitrary curve conversion support.

Input Schema

NameRequiredDescriptionDefault
kindNo
nameYes
actionYes
splinesNo
approvedNo
settingsNo
output_nameNo
expected_snapshot_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description does carry useful weight: 'atomic', snapshot-gated updates, source-preserving conversion, and an explicit limitation of the verified contract. However, for a three-action mutation tool it omits whether create/update overwrite an existing datablock, what happens on a snapshot mismatch, and what the `approved` flag gates.

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?

Four short sentences, front-loaded with the capability statement, with zero filler. The telegraphic noun-phrase style ('Finite atomic curve/text create/update or evaluated copy_to_mesh') slightly hurts first-read parseability but earns its space.

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?

Covers the main complexity of a nested, multi-branch, 8-parameter tool and flags environment limits. Gaps remain for a tool with no annotations and no output schema: the `approved` gate, the snapshot id returned for follow-up updates, and error/rollback behavior are unstated.

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 0% across 8 parameters including nested spline objects, so the description must compensate; it does explain expected_snapshot_id ('current snapshot'), output_name (converted copy), and the spline/text/bevel parameter families. The boolean `approved` parameter is never mentioned, and nothing clarifies name reuse or kind/splines interaction, leaving real gaps.

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?

States specific verbs (create/update/copy_to_mesh) against a specific resource (curve/text) and enumerates what can be authored: Bezier/poly/NURBS splines, control points, text body/settings, bevel/extrusion. It does not name the sibling tools (create_curve, create_curve_or_text, inspect_curve_geometry), so an agent must infer the boundary itself.

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?

Gives one hard prerequisite ('Update requires current snapshot') and one scope exclusion ('not arbitrary curve conversion support'), which implicitly routes agents elsewhere for general conversion. There is no explicit when-to-use-this-vs-sibling guidance, and the copy_to_mesh action's usage condition is only described in terms of its effect ('converted copy preserves source').

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