Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

world_gizmo_scale_prove_roundtrip

Measures and restores two Gizmo Scale increments for the selected pattern UUID to verify a roundtrip scale change in Marvelous Designer scenes.

Instructions

Measure and restore two Gizmo Scale increments for the current selected pattern UUID.

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": {
      "scene_token": "<scene_token>",
      "request_id": "<request_id>",
      "roi_px": "<roi_px>",
      "pattern_uuid": "<pattern_uuid>"
    },
    "name": "world_gizmo_scale_prove_roundtrip"
  }
}

Input Schema

NameRequiredDescriptionDefault
roi_pxYes
request_idYes
scene_tokenYes
pattern_uuidYes
increase_stepsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior1/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: 'restore' implies a state mutation but the description never says whether the scale is temporarily changed and reverted, whether the operation is safe or reversible, what happens if the roundtrip fails, or what side effects occur on the scene. It also ignores the required scene_token, which strongly suggests the tool binds to a live scene that could be affected.

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?

It is a single sentence with no padding, so nothing is wasted, but the brevity comes at the cost of under-specification rather than efficiency. The key scope information is front-loaded, which is the one structural strength.

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, four-required mutation tool with no annotations, no output schema, and no parameter documentation, the definition is far too thin to call correctly. An agent would not know what a successful roundtrip returns, how to size roi_px, or how request_id is used for correlation.

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% across five parameters, and the description only gestures at one of them ('pattern UUID'), without clarifying whether that refers to the pattern_uuid parameter or the editor's current selection — a meaningful ambiguity. roi_px, request_id, scene_token, and increase_steps receive no explanation at all, so the description fails to compensate for the schema gap.

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 concrete action pair ('measure and restore') and a concrete resource ('Gizmo Scale increments') scoped to 'the current selected pattern UUID', which is more than a restatement of the name. However, it never explains what 'prove roundtrip' means operationally, and it does not distinguish this tool from close siblings such as world_gizmo_scale_recover_pair or world_gizmo_scale_inspect.

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 guidance, no prerequisites, and no mention of any alternative tool or condition under which a sibling should be preferred. An agent must guess whether this is a verification step, a repair step, or a diagnostic.

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