Skip to main content
Glama

blender_furniture

Create furniture and complex objects in Blender, including chairs, tables, beds, sofas, cabinets, shelves, desks, stools, and rooms, with customizable styles, dimensions, and materials.

Instructions

Create furniture and complex objects in Blender.

Supports multiple operations through the operation parameter:

  • create_chair: Create chairs (dining, office, armchair, etc.)

  • create_table: Create tables (dining, coffee, desk, etc.)

  • create_bed: Create beds (single, double, bunk, etc.)

  • create_sofa: Create sofas and couches

  • create_cabinet: Create cabinets and storage

  • create_shelf: Create bookshelves and shelving

  • create_desk: Create desks and workstations

  • create_stool: Create stools and bar stools

  • create_room: Create room with walls, floor, ceiling, windows, doors

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNoFurniture creation operationcreate_chair
nameNoName for the furniture objectFurniture
styleNoStyle (modern, classic, rustic, industrial, etc.)modern
dimensionsNoBase dimensions (width, depth, height)
locationNoPosition coordinates
materialNoMaterial type (wood, metal, fabric, etc.)wood
chair_typeNodining
table_typeNodining
bed_typeNosingle
sofa_typeNothree_seater
cabinet_typeNokitchen
desk_typeNooffice
shelf_typeNobookshelf
stool_typeNobar
room_typeNoliving
lengthNo
widthNo
heightNo
wall_thicknessNo
has_windowsNo
window_countNo
has_doorNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It mentions creating objects but omits details about permissions, state changes, or potential destructive actions. The tool likely creates new objects, but the description does not confirm safety or side effects.

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 description is moderately concise but includes a lengthy list of operations. It could be restructured to front-load essential information more effectively, such as grouping type-specific parameters instead of listing them individually.

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?

Given 22 parameters, no annotations, and low schema coverage, the description is incomplete. It does not cover all parameters sufficiently, nor does it explain the output behavior despite having an output schema. Agents would need to infer many details from parameter defaults alone.

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?

With low schema description coverage (27%), many parameters lack meaningful descriptions (e.g., chair_type, table_type). The description adds some context for the 'operation' parameter but fails to explain other critical parameters like 'dimensions', 'location', or per-type specifics, which would help the agent configure the tool correctly.

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 clearly states 'Create furniture and complex objects in Blender' and enumerates specific operations (e.g., create_chair, create_table), making the tool's purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'construct_object', which have overlapping capabilities.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., 'construct_object', 'blender_scene'). It lacks any 'when to use' or 'when not to use' context, leaving the agent to infer usage from the operation list alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sandraschi/blender-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server