Skip to main content
Glama
Sign In
Blender MCP Ultra

Blender MCP Ultra

by 3bdull4h2008
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

subdivide_mesh

Subdivide selected mesh geometry with adjustable cut count and smooth factor for refined control.

Instructions

Subdivide selected mesh geometry.

Args: object_name: Object name. cuts: Number of subdivision cuts. smooth: Smooth factor (0-1).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "object_name": "<object_name>"
    },
    "name": "subdivide_mesh"
  }
}

Input Schema

NameRequiredDescriptionDefault
cutsNo
smoothNo
object_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations are absent, so the description carries the full burden. It identifies a mutation operation but does not disclose whether the subdivision is destructive/reversible, whether it applies to all selected objects, what happens to existing modifiers, or what errors may occur. The description is minimal but not contradictory.

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

Conciseness5/5

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

The description is short, front-loaded with the purpose, and contains no filler. The compact Args list adds useful semantic detail without repeating schema titles unnecessarily.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple operation, it covers the core purpose and all parameter meanings. However, with no annotations, no output schema, and no usage guidance, it remains minimum-viable and leaves gap around when to use it, selection requirements, and side effects.

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

Parameters4/5

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

Schema description coverage is 0%, and the description compensates by listing all three parameters with brief meanings. It adds 'Number of subdivision cuts' and 'Smooth factor (0-1)' beyond the raw schema types and defaults, though the practical effect of each parameter is not deeply explained.

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?

States a specific verb and resource ('Subdivide selected mesh geometry'), and does not merely repeat the tool name. It is distinguishable from remesh_sculpt or loop_cut by the word 'subdivide', though it doesn't explicitly clarify the subdivision type or exactly how it differs from those siblings.

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 is given about when to use this tool versus alternatives. Given many mesh-editing siblings such as remesh_sculpt, smooth_vertices, and loop_cut, the description provides no selection criteria or exclusions.

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