Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

world_adapter_gizmo_drag

Performs a five-event translation or rotation gizmo drag in the current viewport, then optionally validates the resulting export against a world-mm matrix.

Instructions

Send the fixed five-event drag in current viewport logical pixels, total path <=128px.

Supply points from the current selected target and view. An optional world-mm 4x4 matrix checks the resulting exports in matrix_acceptance. The drag path alone has no calibrated world axis, pivot or angle.

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>",
      "group_name": "<group_name>",
      "view_ref": "<view_ref>",
      "view_fingerprint": "<view_fingerprint>",
      "start": "<start>",
      "activation": "<activation>",
      "end": "<end>",
      "purpose": "<purpose>",
      "scene_token": "<scene_token>"
    },
    "name": "world_adapter_gizmo_drag"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
startYes
purposeYes
view_refYes
budget_msNo
activationYes
group_nameYes
request_idNo
scene_tokenYes
pattern_uuidYes
view_fingerprintYes
matrix_tolerance_mmNo
expected_matrix_world_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the entire disclosure burden. It does valuable work by capping the path at 128px and warning that the drag path alone carries no calibrated world axis, pivot or angle, which is a real behavioral limitation. However it never says whether the gesture mutates the scene, what happens when view_fingerprint is stale, how failures surface, or what the response contains beyond a passing reference to matrix_acceptance.

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?

Four sentences, front-loaded with the core action and the pixel budget, then the preconditions, then the optional matrix check and the key limitation. Dense but no obvious padding. The wording is telegraphic in places, which costs a little readability.

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?

A 13-parameter, 9-required gesture tool with no annotations and no output schema needs a substantial definition. The description covers the pixel-space contract and the matrix-acceptance side channel, but eight parameters and the whole question of mutation, idempotency and response shape are unaddressed.

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 13 parameters (9 required), so the description must compensate. It gives units and bounds for start/activation/end and ties expected_matrix_world_mm plus matrix_tolerance_mm to the matrix_acceptance check, but leaves pattern_uuid, group_name, scene_token, view_ref, view_fingerprint, budget_ms, request_id and the purpose enum entirely unexplained.

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?

States a concrete action and medium: send a fixed five-event drag in current-viewport logical pixels with a 128px path cap. That is far more specific than the name alone and tells an agent this is a synthetic pointer-gesture emitter, not a world-space transform. It stops short of differentiating itself from siblings such as scene_adapter_bezier_drag or md_translate_pattern_world.

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?

Preconditions are implied only: 'Supply points from the current selected target and view' tells the agent the drag must be seeded from an existing selection and the live viewport. There is no explicit when-to-use versus when to prefer a world-space sibling, and no statement about what to do if no target is selected.

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