Skip to main content
Glama

create_uv_sphere

Create a UV sphere in Blender with adjustable segments, rings, radius, and location for precise 3D modeling and scene setup.

Instructions

Create a UV sphere with segment/ring control.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
ringsNo
radiusNo
locationNo
segmentsNo
collectionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/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 behavioral burden and falls well short. It does not say that this is a write operation that adds an object to the scene, which collection the object lands in by default, or what happens if collection/name are omitted.

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?

The single sentence is front-loaded and free of padding, but its brevity comes at the cost of substance rather than from efficient expression. It is under-specified rather than tight.

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?

For a six-parameter mutation tool with no annotations and zero schema description coverage, the description is far too thin. The presence of an output schema excuses it from explaining return values, but not from covering defaults, units, or scene-mutation effects.

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

Parameters2/5

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

Schema description coverage is 0% across six parameters, yet the description only gestures at two of them (segments, rings) and does so tautologically. It says nothing about radius units, the expected format of location (a 3-element array?), the default collection behavior, or what name defaults to.

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?

The description names a specific verb and resource ("Create a UV sphere"), which distinguishes it technically from create_ico_sphere and create_sphere. However, it never states explicitly how it differs from those siblings, so the agent must infer the distinction from the term "UV".

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 and no mention of the sibling primitives (create_ico_sphere, create_sphere) that could substitute for it. The agent gets no criteria for choosing among sphere-creation tools or for knowing what context is required (e.g., an active scene or collection).

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