Skip to main content
Glama

create_cone

Add a cone mesh to a Blender scene with configurable radius, depth, location, and collection for 3D modeling.

Instructions

Create a cone.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
depthNo
radius1No
radius2No
locationNo
collectionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, yet it discloses nothing about side effects, scene/collection placement, permissions, or whether the new object is selected or made active. The only behavioral fact conveyed is that something is created, which the name already implies; the existing output schema covers the return value but not the mutation's effects.

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 one-line description is short but that brevity reflects under-specification rather than economy. There is nothing to front-load because there is essentially no content.

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?

For a 6-parameter creation tool with no annotations, no required fields, and ambiguous parameters, one sentence is wholly inadequate. The presence of an output schema excuses explanation of return values but does nothing to compensate for the missing behavioral and parameter context.

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?

Six parameters with 0% schema description coverage, and the description mentions none of them. Terms like radius1, radius2, depth, and collection are left entirely unexplained — an agent cannot tell that radius2=0 yields a pointed cone or what location format is expected.

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?

"Create a cone" is a verbatim restatement of the tool name create_cone, which is the definition of tautology under the rubric. It does not say what kind of cone (mesh primitive, object, geometry) is produced or how it relates to siblings like create_cube, create_sphere, or create_primitive.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as create_primitive or create_mesh. The agent gets no signal about which of the many sibling creation tools is appropriate for a conical shape.

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