Skip to main content
Glama

create_ico_sphere

Creates an icosphere mesh in Blender with configurable radius, subdivisions, location, and collection for building spherical 3D primitives.

Instructions

Create an icosphere.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
radiusNo
locationNo
collectionNo
subdivisionsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/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 disclosure burden for a mutation tool. It does not say whether the new object is linked to the scene, which collection it lands in by default, whether it becomes selected or active, or what happens if the name collides with an existing object.

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 contains no padding, but for a five-parameter creation tool it is under-specified rather than concise. Brevity here costs information rather than saving it.

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?

An output schema exists, so return values need not be explained. Everything else, however, is missing: no default behavior, no parameter meaning, and no differentiation from two sibling sphere tools, which is inadequate for a tool of this parameter richness.

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 (name, radius, location, collection, subdivisions), and the description says nothing about any of them. Meaningful details such as the units of radius, the expected format of location (3-element array), or what subdivisions controls are entirely absent.

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 tool name almost verbatim: 'Create an icosphere.' It does name a specific resource, but with siblings create_sphere and create_uv_sphere present, it never explains how an icosphere differs from those alternatives, leaving the agent to infer the distinction from the name alone.

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 prerequisite information, and no mention of the closely related create_sphere or create_uv_sphere tools. The agent gets no signal about which sphere primitive to choose in a given situation.

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