Skip to main content
Glama

create_cylinder

Add a customizable 3D cylinder to a Blender scene, specifying radius, depth, vertices, location, name, and collection for modeling workflows.

Instructions

Create a cylinder.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
depthNo
radiusNo
locationNo
verticesNo
collectionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing beyond the bare verb. It does not say whether the object is added to the scene, which collection it defaults to, what units depth/radius use, or whether vertices controls tessellation smoothness vs. faceting.

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 tight but that brevity comes from under-specification rather than efficiency. There is no structure, no front-loaded scoping, and nothing that earns the sentence its place beyond repeating the tool 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?

For a six-parameter creation tool with zero annotation and zero schema-description coverage, the description is completely inadequate. An output schema exists so return values need not be explained, but every input's meaning and the creation's side effects are left unspecified.

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% across six parameters (name, depth, radius, location, vertices, collection), and the description compensates for none of them. Terms like 'vertices' (32 segments?) and the coordinate/unit conventions for 'location' and 'depth' are entirely undocumented.

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 restates the name and title with no additional specificity: 'Create a cylinder' adds nothing about size, placement, or which scene/collection it lands in. It is a tautology rather than a statement of purpose, leaving the agent to infer everything from the tool name and sibling list.

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 mention of how this differs from siblings like create_cone, create_circle, or create_primitive, and no prerequisites or exclusions. The agent must guess based on tool names alone.

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