Skip to main content
Glama
dwgx

Blender Copilot MCP Server

by dwgx

inset_faces

Inset all faces of a mesh by adjusting thickness for inset distance and depth for push in/out, enabling precise control over face geometry.

Instructions

Inset all faces of a mesh. Thickness controls inset distance, depth controls push in/out.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
depthNo
thicknessNo
Behavior2/5

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

Provides basic parameter behavior ('Thickness controls inset distance, depth controls push in/out') but omits critical context: whether it works in object/edit mode, if it requires face selection, if it is destructive, or if it applies to all selected objects. No annotations exist to compensate.

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?

Very short and front-loaded, but misses essential information. Every sentence provides some value, but the brevity sacrifices completeness.

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?

Highly incomplete given the tool's complexity. Lacks details on required mode (edit mode), selection behavior, effect on surrounding geometry, and any restrictions. No output schema or annotations to fill gaps.

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

Parameters3/5

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

Adds meaningful descriptions for two of three parameters ('depth' and 'thickness') beyond the schema titles, but does not explain 'name'. With 0% schema description coverage, the description partially compensates but leaves a gap.

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?

Clearly states the action 'Inset all faces of a mesh', which is a specific verb and resource. However, it does not distinguish from siblings like 'extrude_faces' or 'bevel_edges', but 'inset_faces' has no direct sibling, so differentiation is less critical.

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?

No guidance on when to use this tool versus alternatives such as 'extrude_faces' or 'bevel_edges'. Does not mention required context like edit mode or face selection.

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/dwgx/blender-copilot'

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