Skip to main content
Glama

create_plane

Create a plane in Blender with configurable size, location, collection, and optional name to start or extend 3D modeling workflows.

Instructions

Create a plane.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
sizeNo
locationNo
collectionNo

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, the description carries the full burden and discloses nothing: no default size/location behavior, no statement of what collection the plane is added to, no side effects, no confirmation of whether an object is created in the scene. A mutation tool with zero behavioral context.

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 sentence is short with no wasted words, but it is under-specified rather than concise. Brevity here reflects missing content, not efficient communication.

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?

An output schema exists so return values need not be explained, but the four undocumented parameters and total absence of behavioral detail leave the definition inadequate for a creation tool with defaults and scene side effects.

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 four parameters (name, size, location, collection). The description mentions none of them, so the agent gets no meaning for units of 'size', the coordinate space of 'location', or what 'collection' refers to.

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 'Create a plane.' essentially restates the tool name and adds no specificity. In a catalog full of primitive-creation siblings (create_cube, create_circle, create_cone), it gives no basis to distinguish what kind of plane is created or how it differs from other primitives.

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?

No when-to-use guidance, no mention of alternatives such as create_mesh or create_object, and no prerequisites or exclusions. The agent learns nothing about selecting this tool over its many siblings.

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