Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

cloth_probe_runtime

Inspect cloth and REST API signatures in the current Marvelous Designer runtime to confirm available operations before editing or verifying a scene.

Instructions

Inspect cloth and Rest API signatures for the current MD runtime.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cloth_probe_runtime"
  }
}

Input Schema

NameRequiredDescriptionDefault
scene_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/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 behavioral burden, and it discloses almost nothing. 'Inspect' weakly implies a read-only probe, but there is no statement about whether it mutates state, requires an open scene or active MD session, has side effects, or is cheap to call. For a runtime-probing tool with zero annotation coverage this is a significant gap.

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?

A single short sentence with no padding, which is good, but it is under-specified rather than concise. The ambiguous 'Rest API' phrasing and the missing detail mean the brevity costs more than it saves.

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 runtime-probe tool with an undocumented optional parameter, no annotations, and no output schema, the description should say what is returned and under what conditions it works. None of that is present, so an agent would be calling it essentially blind.

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% and the single optional parameter 'scene_token' is never mentioned in the description. The agent gets no guidance on what a scene token is, how to obtain one, or what happens when it is omitted (the default null presumably means 'current scene', but that is left to inference). This is one of the few places the description could have added real value and it does not.

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 verb 'Inspect' and the object 'cloth and Rest API signatures' give a rough sense of the operation, and the phrase 'for the current MD runtime' scopes it. But 'Rest API signatures' is ambiguous (REST endpoints vs. cloth rest-state data), so an agent cannot be certain whether this returns HTTP API metadata or simulation rest-shape data. Siblings like cut_probe_runtime and mesh_probe_runtime suggest a family of runtime probes, but the description does nothing to differentiate this one from them.

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 statement of when this probe should be called versus alternatives such as cloth_rest_shape or cloth_vertex_context_inspect. No prerequisites, no exclusions, no mention of what a caller should do with the result. The agent must infer usage entirely 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