Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

cloth_get_positions

Reads current world XYZ positions in millimeters and optionally returns OBJ vertex references or topology metadata for a Marvelous Designer cloth pattern.

Instructions

Read current world XYZ in mm and optionally issue scene-, topology-, and pose-bound OBJ vertex references. Use vertex_indices to select compact OBJ rows, or [] for topology metadata. References identify exported 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": {
      "pattern_uuid": "<pattern_uuid>"
    },
    "name": "cloth_get_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
scene_tokenNo
pattern_uuidYes
vertex_indicesNo
include_vertex_refsNo
probe_native_getterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 discloses that the tool reads current positions and can optionally return OBJ vertex references. However, it does not clarify whether the operation is strictly side-effect free, what failure behavior looks like, or how scene/topology/pose binding affects results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loads the core read behavior and units. The final sentence adds little and the middle sentence is useful but dense with unexplained terminology.

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 five-parameter tool with no annotations, no output schema, and 0% schema description coverage, the description is materially incomplete. It provides useful hints but does not explain most parameters or the shape of returned data.

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

Parameters2/5

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

Schema description coverage is 0% for five parameters, so the description should compensate, but it only explains vertex_indices and the [] topology-metadata case. It leaves scene_token, pattern_uuid, include_vertex_refs, and probe_native_getter unexplained.

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 description states a specific read operation returning current world XYZ in millimeters and optionally OBJ vertex references. It is clear enough to identify the tool, but it does not distinguish this getter from the similarly named sibling cloth_read_scene_positions.

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 parameter-level guidance for vertex_indices but does not explain when to use this tool instead of alternatives such as cloth_read_scene_positions or cloth_vertex_context_inspect. No exclusions or prerequisites are stated.

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