Skip to main content
Glama

create_torus

Creates a torus mesh in a Blender scene with configurable name, location, collection, and radii for 3D modeling and shape setup.

Instructions

Create a torus.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
locationNo
collectionNo
major_radiusNo
minor_radiusNo

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?

With no annotations provided, the description carries the full burden of behavioral disclosure and delivers none of it. It does not say whether the object is added to the current scene, which collection it lands in, whether it requires an active collection, or what units location and radii use.

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 compact and front-loaded, but this is under-specification rather than conciseness. There is no wasted wording because there is almost no wording at all.

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 five-parameter creation tool with no annotations and zero schema coverage, the description is far too thin. The existence of an output schema excuses it from explaining return values, but nothing else an agent needs in order to call it correctly is present.

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 five parameters, so the description must compensate and instead says nothing. The meaning of major_radius vs minor_radius, the coordinate space of location (an array of numbers), and the role of collection versus name are all left for the agent to guess.

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 torus" states a verb and a resource, but it essentially restates the tool name and adds no distinguishing detail against siblings like create_circle, create_sphere, or create_primitive. An agent can infer it makes a torus, but nothing about scope, output, or which create_* primitive tool to prefer.

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 mention of alternatives among the many create_* siblings, and no prerequisites. The description offers nothing an agent could use to route between this and create_primitive or create_circle.

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