Skip to main content
Glama

remesh_mesh

Applies a remesh modifier to a named mesh and bakes it, letting you rebuild topology with configurable mode and octree depth.

Instructions

Apply remesh via modifier and apply it.

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

Input Schema

NameRequiredDescriptionDefault
modeNoSMOOTH
nameYes
octree_depthNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/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 behavioral burden. "Apply it" hints that a modifier is committed (a mutation), but the description does not say whether the operation is destructive, whether it replaces existing topology, whether it requires an active object, or how expensive it is at higher octree depths.

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?

It is short, but the brevity comes at the cost of clarity: a single sentence with redundant wording and no front-loaded statement of what remeshing actually does. Length is fine; the structure wastes the little space it has.

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. However, for a destructive topology-changing operation with three undocumented parameters and no annotations, the description omits nearly everything an agent needs to call it correctly or safely.

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 all three parameters (name, mode, octree_depth) are undocumented in both schema and description. Critically, the valid values for mode are never listed despite mode being the primary control over remesh behavior, and octree_depth's effect on detail/performance is unexplained.

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?

"Apply remesh via modifier and apply it" largely restates the tool name and repeats "apply" twice, leaving the actual operation vague. It never distinguishes remeshing from siblings like decimate_mesh, subdivide_mesh, or smooth_mesh, so an agent cannot tell which is appropriate from the description alone.

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 exclusions, and no mention of alternatives such as decimate_mesh or smooth_mesh. The agent is left to infer that remeshing rebuilds topology, which is not stated anywhere.

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