Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

md_rotate_pattern_world

Rotates an entire pattern around a specified world-space axis and pivot, using explicit coordinates and optional verification to preserve geometry, UVs, and groups.

Instructions

Right-hand rotate a whole pattern around an explicit WORLD axis/pivot.

axis_world is a nonzero three-number direction, normalized internally. angle_degrees is finite and in [-360, 360]; pivot_world_mm is an explicit three-number WORLD point in mm, never an inferred centroid. For the ring route, capture the selected pattern with include_mesh and supply that request ID, physical PNG ROI and three calibrated logical viewport points. Omit ring_color for blue/Z. Red/X and green/Y require a color-qualified path from the current frame. The positions profile verifies the same vertex tolerance and preservation of UV, topology and other groups. It also reports the separate normal error. For a calibrated enlarged red path, supply gizmo_scale_steps=2 and expanded_ring_support_sha256 from the qualified enlarged frame. Enable include_assigned_topstitch to refresh one bound Texture Topstitch and verify both groups against the same requested matrix.

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>",
      "axis_world": "<axis_world>",
      "angle_degrees": "<angle_degrees>",
      "pivot_world_mm": "<pivot_world_mm>"
    },
    "name": "md_rotate_pattern_world"
  }
}

Input Schema

NameRequiredDescriptionDefault
ring_planNo
axis_worldYes
request_idNo
scene_tokenNo
pattern_uuidYes
tolerance_mmNo
angle_degreesYes
pivot_world_mmYes
verification_profileNostrict
include_assigned_topstitchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it states axis normalization, a finite angle range of [-360, 360], that the pivot is always explicit and never an inferred centroid, and what the positions profile actually verifies (vertex tolerance plus preservation of UV, topology and grouping) with a separate normal error. Gaps remain on the mutation side — nothing about reversibility/undo, authorization, or what happens on verification failure — which keeps it below a 5.

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 correct operation-scoping sentence is front-loaded, which is good, but the remainder is a dense block of conditional fragments with no separation between the core rotation semantics and the optional ring/path verification modes. Terse clauses like 'Omit ring_color for blue/Z' and 'Red/X and green/Y require a color-qualified path' demand prior domain context to parse and read as compression rather than clarity.

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 10-parameter mutation tool with a nested ring plan, two verification profiles and no annotations and no output schema, the description covers the advanced routes well but leaves core items unaddressed: the meaning of pattern_uuid/scene_token/tolerance_mm, whether the rotation is reversible, and how verification failures surface. An agent could invoke the basic path correctly but would be guessing on several parameters and on recovery behavior.

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 is the only source of parameter meaning and it explains axis_world, angle_degrees, pivot_world_mm, the ring_plan sub-fields (frame_request_id, roi_px, three calibrated logical viewport points, ring_color, gizmo_scale_steps, expanded_ring_support_sha256), verification_profile, and include_assigned_topstitch. Several parameters go entirely unexplained — pattern_uuid, scene_token, request_id and tolerance_mm — which leaves meaningful holes at 10 parameters and 0% coverage.

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 opening sentence gives a specific verb and resource ('Right-hand rotate a whole pattern') plus an explicit scope qualifier (WORLD axis/pivot), which cleanly separates it from translation or reconciliation work. It stops short of naming a sibling such as md_reconcile_world_rotation, so an agent must infer the boundary from tool names alone.

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 provides conditional guidance inside this tool's own parameter space (when to use the ring route, when to omit ring_color, when to use the positions profile, when to supply an enlarged red path), which is useful. However, it never states when to choose this tool over md_translate_pattern_world or md_reconcile_world_rotation, nor any prerequisites such as an open project or a selected pattern, so alternative-tool routing is left to inference.

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