Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

md_translate_pattern_world

Translate a single Marvelous Designer pattern by an exact world-space millimetre offset and verify target vertices while checking non-target geometry remains unchanged.

Instructions

Translate one current pattern by [dx, dy, dz] in WORLD millimetres.

delta_mm has exactly three finite numbers. Executes once only when a native world backend is configured; verifies every target vertex and unchanged non-target geometry/invariants. Never uses arrangement offsets, project import/export, simulation, or automatic restoration.

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>",
      "delta_mm": "<delta_mm>"
    },
    "name": "md_translate_pattern_world"
  }
}

Input Schema

NameRequiredDescriptionDefault
delta_mmYes
request_idNo
scene_tokenNo
pattern_uuidYes
tolerance_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 discloses the single-execution semantics, the backend prerequisite, and the post-condition that all target vertices are verified while non-target geometry and invariants are unchanged. Missing are failure behavior, atomicity/rollback on verification failure, and whether the operation is destructive to selection state.

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 purpose is front-loaded in the first sentence and the remaining lines add preconditions, guarantees, and exclusions without filler. The line-broken layout is slightly awkward but no sentence is redundant.

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 mutation tool with no annotations, no output schema, and five undocumented parameters, the definition covers preconditions and verification invariants well but leaves the agent guessing on return values, error/rollback semantics, and the purpose of three parameters. It is adequate but not self-sufficient for a confidently correct call.

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% across five parameters, so the description must compensate. It does explain delta_mm's constraint ("exactly three finite numbers") and ties pattern_uuid to the "one current pattern" notion, but tolerance_mm, request_id, and scene_token — the parameters governing verification tolerance and idempotency — are never mentioned.

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?

"Translate one current pattern by [dx, dy, dz] in WORLD millimetres" gives a specific verb (translate), a bounded resource (one current pattern), and a unit/frame qualifier (WORLD mm), which cleanly separates it from the rotate sibling and from grid-step translation. It stops short of explicitly naming a contrasting sibling, so it is clear but not fully self-differentiating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Executes once only when a native world backend is configured" states a hard precondition, and the closing exclusion list (arrangement offsets, project import/export, simulation, automatic restoration) tells the agent which alternative paths this tool will not take. It does not say what to do when no native backend is configured, nor point to a fallback sibling, which keeps it below 5.

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