Skip to main content
Glama

triangulate_mesh

Converts a named mesh into triangles to prepare geometry for consistent rendering, simulation, or export.

Instructions

Triangulate 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": "triangulate_mesh"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

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 provided, so the description carries the full burden, yet it discloses nothing beyond the name. It does not say whether triangulation is destructive, whether it replaces the mesh in place or returns a new one, whether quad topology is lost, or what permissions/state are required.

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?

The single sentence is short but that is under-specification rather than conciseness; there is no front-loaded statement of effect, scope, or result. Nothing extraneous exists, but almost nothing useful exists either.

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 explained, but for a topology-mutating operation with no annotations and an undocumented required parameter, the definition leaves the agent unable to call it confidently or predict its 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?

The single parameter "name" has 0% schema description coverage, and the description adds no meaning at all — it never says whether "name" is the object name, the mesh data-block name, or a selection identifier. With one undocumented parameter, the description must compensate and does not.

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?

"Triangulate a mesh" is essentially a restatement of the tool name, expanded only by the resource noun. It conveys the operation type but does not distinguish it from siblings such as remesh_mesh, subdivide_mesh, or decimate_mesh, all of which also alter mesh topology.

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 (edit mode, selection state), and no mention of alternatives like remesh_mesh or subdivide_mesh. The agent must infer the choice entirely from the tool name.

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