Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

cloth_rest_shape

Updates or resets the cloth Rest shape for one selected pattern UUID, using the current 3D state or the pattern reference to correct Rest coordinates.

Instructions

Update Rest from current 3D state or reset the reference for one selected UUID.

The native_archive method requires MD 2026.1.237 minimized with stopped simulation, the existing hidden Rest host in Selected Patterns mode, and one current pattern selected. It checks serialized Rest coordinates against the current ordered OBJ.

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": {
      "pattern_uuid": "<pattern_uuid>",
      "action": "<action>",
      "scene_token": "<scene_token>"
    },
    "name": "cloth_rest_shape"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
methodNonative_archive
request_idNo
scene_tokenYes
pattern_uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose valuable behavior: strict host/version prerequisites and that it validates serialized Rest coordinates against the current ordered OBJ. It does not say whether the rest update is destructive or reversible, what happens when the check fails, or what the tool returns, leaving a mutation's risk profile partly unexplained.

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 purpose is front-loaded in the opening sentence and the prerequisite block is clearly separated as a second paragraph with no filler. The text is efficient overall, though the OBJ-comparison sentence is vague about consequences and could either be sharpened or dropped.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter, unannotated mutation with no output schema, the definition covers the critical environmental preconditions well, but the gaps in scene_token/request_id semantics and the missing failure/return behavior keep it from being complete enough to call confidently in edge cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, so the description must compensate. It covers action modes (implicitly mapping to update_from_current and reset_to_pattern) and pattern_uuid ('one selected UUID'), and names the method value native_archive, but scene_token and request_id are never explained, leaving meaningful gaps.

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

Purpose4/5

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

The first sentence names a specific verb and resource: update/rest reference for one selected UUID, and enumerates the two modes (from current 3D state, or reset to pattern) that match the action enum. It does not explicitly contrast with the similar-sounding sibling cloth_reconcile_rest_archive, so an agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a real precondition block for the native_archive method (MD 2026.1.237 minimized, stopped simulation, hidden Rest host in Selected Patterns mode, one current pattern selected), which tells the agent when the call can succeed. However, it offers no guidance on choosing between the two actions or on when to use this tool versus cloth_reconcile_rest_archive or the rest_* inspection 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