Skip to main content
Glama

decimate_mesh

Reduce polygon count on a Blender mesh by applying an adjustable decimation ratio, simplifying geometry for lighter scenes and rendering.

Instructions

Decimate a mesh.

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": "decimate_mesh"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
ratioNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses nothing: not that the operation mutates/replaces the mesh, not whether it is reversible, not how the ratio affects geometry quality or topology, and not any preconditions. Four words provide zero behavioral signal for a destructive mesh operation.

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

Conciseness2/5

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

Brevity here is under-specification rather than conciseness; the single sentence has no front-loaded scoping or qualifying detail. There is nothing superfluous, but the sentence does not earn its place as a usable definition.

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?

An output schema exists, so return values need not be described, but for a mesh-mutating tool with no annotations and 0% parameter coverage the definition is far too thin. An agent cannot call this correctly without guessing the meaning of ratio and the operation's side effects.

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% for both parameters, and the description compensates for none of it. The critical 'ratio' parameter (default 0.5) is never explained, so the agent cannot know whether it means fraction retained, fraction removed, or target face count.

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

Purpose2/5

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

"Decimate a mesh" restates the tool name with a verb and resource but adds no meaning: it never says what decimation does (reduce polygon count) or how it differs from nearby tools like remesh_mesh, mesh_cleanup, or subdivide_mesh. An agent can guess the general area but must infer the actual effect.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. Nothing indicates whether to reach for this instead of remesh_mesh or mesh_cleanup, nor whether a modifier or applied geometry should already exist.

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