Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

create_text

Creates 2D or 3D Bezier/NURBS curves, circle paths, and text objects in the active Blender scene, with configurable extrusion, bevel, resolution, dimensions, 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_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?

No annotations are provided, so the description carries the full behavioral burden. It says 'in the active scene' but does not disclose mutation side effects, what happens if the required unique name already exists, whether the operation is reversible, required scene state, or any permission or error conditions.

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?

The description is two sentences, front-loaded with the action and resource, with no filler. The second sentence largely restates schema fields, which is mildly redundant but not costly.

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?

This is a 12-parameter creation tool with no annotations and no output schema, so the description should do more to explain required context, name uniqueness behavior, side effects, and return value expectations. It leaves significant gaps for an agent invoking a mutating scene tool.

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 already has an inline description. The prose lists features like dimensions, extrude depth, bevel depth, resolution, and text body, but this merely mirrors the schema and adds no syntax, constraints, or interpretation beyond what the schema provides. Baseline 3 is appropriate.

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 states a specific verb and resources: 'Create 2D or 3D Bezier/NURBS curves, circle paths, or text objects in the active scene.' It is clear what the tool does, but it does not differentiate itself from sibling creation tools such as create_curve, create_curve_or_text, or create_vse_text_strip.

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 explicit when-to-use guidance, no conditions for choosing this tool over the many sibling creation tools, and no exclusions. The phrase 'in the active scene' implies context but does not help an agent decide between this and create_curve or create_curve_or_text.

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