Skip to main content
Glama
dwgx

Blender Copilot MCP Server

by dwgx

curve_create_bezier

Create a Bezier curve by defining control points with handles, or generate a default S-curve. Customize fill mode, bevel depth, and resolution.

Instructions

Create a Bezier curve with custom control points.

Args: name: Object name points: List of control point dicts: [{"co": [x,y,z], "handle_left": [x,y,z], "handle_right": [x,y,z], "type": "AUTO"}] If empty, creates a default S-curve. location: Object location [x, y, z] fill_mode: FULL, BACK, FRONT, HALF, NONE bevel_depth: Bevel depth for tube-like appearance bevel_resolution: Bevel smoothness resolution_u: Curve resolution extrude: Extrude amount for flat ribbon

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoBezierCurve
pointsNo
extrudeNo
locationNo
fill_modeNoFULL
bevel_depthNo
resolution_uNo
bevel_resolutionNo
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as side effects, creation behavior (e.g., whether it modifies existing objects or only creates new ones), or any required permissions. It only describes parameters.

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 front-loaded with the main purpose and then lists parameters in a clear, structured Args format. Each parameter is briefly described without unnecessary words, though the block format could be more concise.

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?

Given the complexity (8 parameters, no required, no output schema, no annotations), the description covers parameters adequately but fails to explain return values, side effects, or selection state after creation. This leaves gaps for an AI agent to fully understand tool behavior.

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

Parameters4/5

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

The description adds significant meaning beyond the schema: it explains the structure of 'points' with a detailed format and default S-curve behavior, and lists enum options for fill_mode. This compensates for the 0% schema description coverage indicated in context.

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?

The description explicitly states 'Create a Bezier curve with custom control points', clearly identifying the verb (create) and resource (Bezier curve). It distinguishes from sibling tools like curve_create_circle and curve_create_nurbs by specifying the curve type.

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?

The description implies usage for custom Bezier curves but does not explicitly state when to use this tool versus alternatives like NURBS or path curves. No exclusions or prerequisites are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dwgx/blender-copilot'

If you have feedback or need assistance with the MCP directory API, please join our Discord server