Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

create_curve_or_text

Create 2D or 3D Bezier/NURBS curves, circle paths, or text objects in the active Blender scene with adjustable dimensions, extrusion, bevel, 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_or_text"
  }
}

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?

With no annotations supplied, the description carries the full burden and does not meet it. It implies mutation (object creation) but says nothing about permissions, name-collision behavior, whether existing selection or geometry is affected, or what is returned on success or failure.

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 sentences, front-loaded with the core action and resource types, with no filler. The second sentence largely inventories parameters already in the schema, which is mild redundancy but not harmful.

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?

For a 12-parameter creation tool with no annotations and no output schema, the description is thin. It omits placement parameters (location, rotation, scale), naming/uniqueness rules, and the practical meaning of the deprecated 'approved' flag, leaving the agent to infer the full call contract from the schema alone.

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 one of the 12 parameters is already documented in the schema, and the baseline of 3 applies. The description echoes the field families (dimensions, extrude, bevel, resolution, body) but adds no syntax, units, or constraint information beyond what the schema states.

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 uses a specific verb ('Create') and names the resources precisely: 2D/3D Bezier/NURBS curves, circle paths, and text objects in the active scene. It does not differentiate from the sibling tools create_curve and create_text, so an agent cannot tell from the text alone why this combined tool should be chosen over those.

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, and no alternatives are named. The only usage context is the implicit 'in the active scene', which is a location, not a selection rule.

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