Skip to main content
Glama

smooth_mesh

Adjust mesh vertices with factor and repeat controls to reduce jagged edges and refine surface geometry in Blender.

Instructions

Smooth mesh vertices.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
factorNo
repeatNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It implies a mutation of vertex positions, but says nothing about whether it operates on the whole mesh or a selection, whether results are reversible or destructive, or whether prior modifiers/state are affected. Only the fact that it modifies vertices is communicated.

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 sentence is free of padding, but it is severely under-specified rather than concise. A four-word description cannot front-load the information an agent needs to invoke this mutation tool correctly.

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?

The presence of an output schema removes the need to explain return values, but for a three-parameter mutation tool with no annotations and zero schema documentation, the description is far too thin. It leaves scope, effect, and parameter behavior entirely undocumented.

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 mentions none of them. It does not explain what 'name' identifies, what 'factor' controls (strength vs. blend), or how 'repeat' iterates the smoothing, leaving every parameter's meaning to guesswork.

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 names a specific verb and resource ('Smooth mesh vertices'), so the basic operation is identifiable. However, it gives no detail on what smoothing means here (relax/laplacian/filter) and does nothing to distinguish it from adjacent siblings such as subdivide_mesh or remesh_mesh.

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, when-not-to-use, or alternative-tool guidance. An agent must infer that this is the right choice over bevel_mesh, decimate_mesh, or mesh_cleanup purely 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