Skip to main content
Glama

subdivide_mesh

Subdivide mesh faces in Blender to add detail and geometry for smoother modeling. Specify the mesh name and number of cuts to refine shapes directly.

Instructions

Subdivide mesh faces.

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": {
      "name": "<name>"
    },
    "name": "subdivide_mesh"
  }
}

Input Schema

NameRequiredDescriptionDefault
cutsNo
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It reveals nothing about whether the mesh is modified in place, whether the operation is destructive or reversible, what happens to existing face data, or whether a specific mode or selection is required. Only the existence of an output schema reduces the need to describe the return value.

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 single fragment is short and front-loaded, with no wasted words. However, it is so terse that its brevity works against the agent: it is under-specified rather than economical.

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?

For a two-parameter mesh-editing tool with no annotations and no schema documentation, the definition is incomplete. An agent is left not knowing what 'cuts' controls, what 'name' identifies, or whether the edit is in place. Only return values are covered indirectly, by the output schema.

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%, and the description does not mention either parameter. The meaning of 'name' (target mesh object?) and 'cuts' (number of subdivision iterations/segments, default 1) is left entirely unexplained. At zero coverage the description needed to compensate and does not.

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 states a specific verb and resource: subdividing the faces of a mesh. That is enough for an agent to tell it apart from siblings such as bevel_mesh, decimate_mesh or remesh_mesh. It does not say which subdivision algorithm (simple versus Catmull-Clark) is used, so the purpose is clear but not fully precise.

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?

There is no statement of when to use this tool, when not to, or which sibling to choose instead. An agent must infer that this tool is preferred over remesh_mesh or smooth_mesh for increasing face density. No prerequisite state (for example entering edit mode) is described.

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