Skip to main content
Glama

create_circle

Creates a circular mesh in Blender with configurable radius, vertex count, location, and target collection for 3D modeling.

Instructions

Create a circle.

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_circle"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
radiusNo
locationNo
verticesNo
collectionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/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, yet it discloses nothing: not the coordinate system, units, whether the circle is a mesh or curve, what the defaults mean, or whether the object is added to the scene. For a mutation tool with zero annotation coverage this is a severe gap.

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

Conciseness2/5

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

The single sentence is short but this is under-specification rather than conciseness. Nothing is front-loaded because there is nothing to front-load beyond the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values need not be described, but a 5-parameter creation tool with defaults and no annotations needs far more. An agent cannot safely invoke this without guessing at radius units, location format, and vertices semantics.

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?

Five parameters (name, radius, location, vertices, collection) have 0% schema description coverage, and the description supplies no meaning for any of them. It does not explain units for radius, the expected format of location, what vertices controls (tessellation), or what collection scopes the result to.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is essentially a restatement of the tool name: 'Create a circle' adds no qualifier about which circle primitive, mesh vs curve, or scene context. It gives a verb and a resource but nothing that distinguishes it from create_uv_sphere, create_torus, create_primitive, or the many other create_* siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no routing to alternatives such as create_primitive or create_curve. An agent has no basis beyond the name to decide when this tool is the right choice.

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