Skip to main content
Glama
Sign In
blender-mcp

blender-mcp

by kleer001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_curve

Create curve objects in Blender with BEZIER, NURBS, and POLY types, setting name and location for scene placement.

Instructions

Create a curve object. Types: BEZIER, NURBS, POLY (path).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
typeNoBEZIER
locationNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are present, so the description carries the full behavioral burden. It only states the action and types; it does not disclose side effects, whether an existing object is replaced, how name/location defaults behave, or what is returned. For a mutation tool this is insufficient context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise—two short sentences with no filler. It front-loads the action and packs the type enum compactly, making every word earn its place.

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?

This is a simple, no-required-parameter creation tool with an output schema, so the description does not need to discuss return values. However, it omits behavioral context and leaves location semantics unclear, making it only marginally complete for an agent that must invoke the tool correctly.

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

Parameters2/5

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

The description partially compensates for the 0% schema coverage by enumerating valid values for the type parameter, but it says nothing about name or location semantics. Since location is an array of numbers with no explanation, the agent must guess its meaning from the parameter name.

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 uses a specific verb ('Create') and a clear resource ('curve object'), and it distinguishes this tool from generic create_object by explicitly listing the supported curve types (BEZIER, NURBS, POLY). This makes the tool's purpose immediately clear.

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?

Usage is implied by the description ('Create a curve object'), so an agent can infer it is for curves rather than other object types. However, there is no explicit statement of when to use this tool versus alternatives like create_object, and 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.

Deploy Server

Other Tools