Skip to main content
Glama

create_curve

Create a Bezier curve in Blender with optional name, location, and collection settings to build editable paths for modeling or animation.

Instructions

Create a Bezier curve.

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
locationNo
collectionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/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 disclosure burden and delivers almost nothing: it does not say whether the curve is added to the scene root or a collection, whether defaults are applied when location/collection are omitted, or whether the curve is editable afterwards. The only behavior conveyed is that the call creates something, which is already implied by the name.

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

Conciseness3/5

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

A single short sentence with no filler, but its brevity reflects under-specification rather than discipline. There is nothing to front-load because nothing beyond the bare purpose was included.

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?

An output schema exists, so return values need not be explained, but for a creation tool with three undocumented optional parameters and no annotations this description is far too thin. An agent cannot tell what defaults apply or how the new curve is placed without trial and error.

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

Parameters1/5

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

Schema description coverage is 0% for three parameters (name, location, collection), and the description adds no meaning for any of them—nothing on whether name is auto-generated, what coordinate space location uses, or what a collection value should reference. With zero coverage in both places, the parameter semantics are effectively undocumented.

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?

States a specific verb plus a concrete resource ("Create a Bezier curve"), which is enough for an agent to distinguish it from primitive-creation siblings like create_circle or create_cube. It stops short of any sibling differentiation or scope detail, but the core purpose is unambiguous.

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?

No when-to-use guidance, no preconditions, and no pointer to alternatives such as create_circle or create_mesh. The agent must infer entirely on its own when a Bezier curve is the right primitive to create.

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