Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

cloth_set_positions

Set cloth vertex positions to absolute world XYZ in mm via meshbox_plane, then verify scene OBJ after writing. Use pattern UUIDs and vertex references to calibrate placement.

Instructions

Request absolute world XYZ in mm. The explicit meshbox_plane method uses one current OBJ vertex reference and a displacement in the current 3D camera plane. Select its pattern UUID in MovePattern/World and frame it for calibration. The method requires a uniquely resolved 2D outline and verifies the complete scene OBJ after writing.

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>",
      "targets": "<targets>",
      "scene_token": "<scene_token>"
    },
    "name": "cloth_set_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodNo
targetsYes
request_idNo
scene_tokenYes
pattern_uuidYes
tolerance_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/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 of behavioral disclosure. It usefully states that the method requires a uniquely resolved 2D outline and verifies the complete scene OBJ after writing, but it omits mutation semantics, failure behavior, permission requirements, and what happens to existing positions.

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 description is moderately sized but poorly front-loaded: the first sentence is an incomplete statement of intent rather than a clear action. The remaining sentences pack in useful constraints, but the structure requires the reader to reconstruct the tool's main purpose.

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?

For a complex mutation tool with six parameters, nested target objects, no annotations, no output schema, and zero schema description coverage, the description is materially incomplete. It should explain scene_token, tolerance behavior, request_id, target array semantics, and expected outcomes more fully.

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%, so the description must compensate for six undocumented parameters. It partially explains pattern_uuid, method, vertex_ref, and position_mm units, but leaves scene_token, targets structure, request_id, and tolerance_mm semantically 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?

The description opens with "Request absolute world XYZ in mm," which does not clearly state that the tool sets cloth vertex positions. It mentions method-specific behavior and prerequisites, but the core verb+resource relationship remains implicit and depends heavily on the tool name to be understood.

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?

The description gives some setup conditions for the meshbox_plane method, such as selecting the pattern UUID and framing it for calibration, but it never states when to use this tool versus siblings like cloth_get_positions or cloth_read_scene_positions. There are no explicit alternatives or when-not conditions.

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