Skip to main content
Glama

edit_mesh

Applies a specified structured mesh operation to a named object, with optional parameters to control geometry changes.

Instructions

Run a structured mesh edit operation on an object.

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>",
      "operation": "<operation>"
    },
    "name": "edit_mesh"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
paramsNo
operationYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/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. It implies mutation ('edit') but says nothing about supported operations, whether edits are destructive or reversible, permission requirements, or what the 'params' object controls — a serious gap for a write operation with zero annotation coverage.

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 sentence is front-loaded and free of filler, so it is structurally clean. However, its brevity reflects under-specification rather than efficient communication, which keeps it at the minimum-viable level.

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 mutation tool with three parameters, 0% schema description coverage, and no annotations, the description should at least enumerate valid operations and explain 'params'; it does neither.

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% across three parameters, and the description adds no meaning for 'name', 'operation', or 'params'. The critical 'operation' parameter is undocumented — no valid values, format, or examples are given — so the agent must guess.

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

Purpose3/5

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

The description states a verb and resource ('Run a structured mesh edit operation on an object'), but 'structured mesh edit operation' is vague and does not distinguish this tool from specific siblings like bevel_mesh, extrude_mesh, or subdivide_mesh. An agent cannot tell from the text whether this is a generic dispatcher or something else.

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 mention of alternatives, and no exclusions. The definition gives no signal about when to pick edit_mesh over the many operation-specific sibling tools.

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