Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

create_curve

Create 2D or 3D Bezier/NURBS curves, circle paths, or text objects in Blender with configurable dimensions, extrude/bevel depth, resolution, and text content.

Instructions

Create 2D or 3D Bezier/NURBS curves, circle paths, or text objects in the active scene. Supports configurable dimensions, geometry extrude depth, bevel depth, curve resolution, and text body contents.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "create_curve"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoText body content when curve_type is TEXT.Text
nameYesUnique name for the created curve or text object.
scaleNoTarget [x, y, z] scale factors.
extrudeNoGeometric extrusion depth along curve normal in meters.
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
locationNoTarget [x, y, z] location coordinates in meters.
rotationNoTarget [x, y, z] Euler rotation in radians.
curve_typeNoType of curve or text geometry to create.BEZIER
dimensionsNoCurve dimensions (2D or 3D). Defaults to 3D.3D
resolutionNoSurface resolution (U) for curve evaluation.
bevel_depthNoBevel depth applied to the curve in meters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it does not say that this creates and persists a new datablock, whether names must be unique (and what happens on collision), whether the operation is undoable, or what is returned. 'Supports configurable dimensions, geometry extrude depth, bevel depth, curve resolution, and text body contents' just restates schema fields rather than describing behavior. For a 12-parameter mutation tool this is a substantial gap.

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?

Two tight sentences with the creation scope front-loaded and zero filler. Slight deduction because the second sentence is a low-value enumeration of fields the schema already documents, rather than information the agent cannot get elsewhere.

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

Completeness2/5

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

With 12 parameters, no annotations, and no output schema, the definition should carry much more: transform parameters (location/rotation/scale), the deprecated 'approved' flag, and task_id go entirely unmentioned, and there is no statement of success/failure behavior or result. What is present is accurate but far from sufficient for a tool of this complexity.

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 100%, so every parameter is already documented in the schema, and the description merely echoes a subset of them (extrude, bevel depth, resolution, body, dimensions). It adds no meaning beyond the schema, so the baseline 3 applies rather than anything higher.

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 opens with a specific verb and resource set — 'Create 2D or 3D Bezier/NURBS curves, circle paths, or text objects in the active scene' — which maps directly onto the curve_type enum. It is clear what the tool produces, but it offers no differentiation from apparent siblings such as create_curve_or_text or create_text, which an agent would need in order to choose correctly.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. The description never says when to prefer this over create_text, create_curve_or_text, or configure_curve_geometry, nor does it state preconditions such as an active scene or object mode. The only contextual hint is the incidental phrase 'in the active scene'.

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