Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

world_grid_step_translate_axis

Moves a selected pattern along X, Y, or Z by a signed millimetre distance via a temporary Grid step, then verifies the move and restores protected Grid settings.

Instructions

Move the current selected pattern along one axis using a temporary Grid step.

Select the current pattern in Front for X/Y or Left for Z. Uses signed millimetres with one decimal place, reads the moved OBJ, and verifies restoration of the original Grid field and property page. The exported groups must bind uniquely. Other panels and their accessories are protected. The optional position profile independently verifies XYZ and bounds each target OBJ normal component to one six-decimal quantum. A failed matrix check can include a measured move and a restored Grid.

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": "<axis>",
      "distance_mm": "<distance_mm>",
      "scene_token": "<scene_token>",
      "request_id": "<request_id>"
    },
    "name": "world_grid_step_translate_axis"
  }
}

Input Schema

NameRequiredDescriptionDefault
axisYes
request_idYes
distance_mmYes
scene_tokenYes
pattern_uuidYes
verification_profileNostrict

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 discloses the temporary Grid step, reads back the moved OBJ, verifies restoration of the original Grid field and property page, requires unique group bindings, protects other panels, and explains the optional position profile and what a failed matrix check can return. Gaps remain around whether the move is persisted or rolled back, permissions, and failure/error modes.

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 purpose is front-loaded in the first sentence, which is good, but the remainder is a dense run-on of jargon ('one six-decimal quantum', 'a restored Grid') and hard line breaks. Some sentences, notably 'A failed matrix check can include a measured move and a restored Grid', are ambiguous and cost more reader effort than they return.

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 six-parameter, no-annotation, no-output-schema mutation tool, the description covers behavior and verification semantics but omits the meaning of the token/ID parameters and any sense of what a successful call returns. It is adequate for a domain-expert agent but not self-sufficient.

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 coverage is 0%, so the description must compensate, and it partially does: it conveys that distance is signed millimetres with one decimal place, that axis maps to Front for X/Y and Left for Z, and that verification_profile independently verifies XYZ and quantizes OBJ normals to six decimals. It says nothing about pattern_uuid, scene_token, or request_id, leaving three of six parameters undocumented anywhere.

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 first sentence states a specific verb and resource: move the selected pattern along one axis via a temporary Grid step, which is precise enough to distinguish it from a generic translate. It never names the closest siblings (e.g. md_translate_pattern_world or world_grid_step_recover_axis) to explain how this differs, so sibling differentiation is left to inference.

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?

It gives a real precondition, 'Select the current pattern in Front for X/Y or Left for Z', which an agent needs before calling. However, there is no statement of when to prefer this over the plain world-translate tool or the recover_axis sibling, and no explicit when-not guidance; usage is implied rather than directed.

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