Skip to main content
Glama

blender_furniture

Create furniture and complex objects in Blender.

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations provide no safety hints (all false). The description only says 'in Blender' and 'create', without disclosing side effects, whether it modifies the current scene, or any permissions needed. No additional behavioral context is provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and well-structured with a bullet list of operations, front-loading the core purpose. It avoids unnecessary prose, though it could have added brief parameter guidance without becoming verbose.

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 the high complexity (22 parameters, many operation-specific) and low schema coverage, the description is incomplete. It does not explain how operation selection affects parameters, room creation specifics, or any output behavior. An output schema exists, but that does not cover usage semantics for each operation.

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 only 27%, so the description must compensate for poorly documented parameters. It does not explain which parameters apply to which operation, nor does it add meaning beyond listing operation values. This leaves many type-specific parameters (e.g., bed_type, has_door) ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates furniture and complex objects in Blender, with a specific verb and resource. Listing supported operations (chairs, tables, beds, sofas, etc.) distinguishes it from sibling tools by targeting a specific object category.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by listing supported operations, so an agent knows this tool is for furniture creation. However, it lacks explicit guidance on when to use this tool versus alternatives like construct_object or blender_mesh, and does not mention exclusions or prerequisites.

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

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