Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

world_adapter_arrow_step

Sends one screen-relative Qt arrow press/release and reads both complete scene exports, with optional post-dispatch world-mm matrix verification.

Instructions

Send one screen-relative Qt arrow press/release and read both complete scene exports.

An optional 4x4 world-mm translation matrix is checked after dispatch. Read result.matrix_acceptance for the comparison. The matrix does not select a direction or step size. Position tolerance is at most .002 mm. Pass canonical_view to verify the world axes immediately before input.

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>",
      "direction": "<direction>",
      "scene_token": "<scene_token>"
    },
    "name": "world_adapter_arrow_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
view_refYes
budget_msNo
directionYes
group_nameYes
request_idNo
scene_tokenYes
pattern_uuidYes
canonical_viewNo
view_fingerprintYes
matrix_tolerance_mmNo
expected_matrix_world_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations the description must carry the full burden, and it does disclose real behavior: the input is dispatched unconditionally and the matrix comparison happens after dispatch, read back via result.matrix_acceptance, with a .002 mm position tolerance. It omits key traits for a probable mutation tool -- whether the scene changes, what happens when the matrix check fails, and what budget_ms/request_id do.

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?

Front-loaded with the action in the first sentence, then verification details, with minimal filler. The phrase 'read both complete scene exports' is slightly opaque about what the two exports are, which costs a point but not much.

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 an 11-parameter tool with no annotations and no output schema, the description leaves most required identifiers unexplained and never states what a failed matrix acceptance means or what the caller should do. Referencing result.matrix_acceptance is helpful since no output schema exists, but overall coverage is thin.

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 11 parameters, so the description must compensate and largely does not. It adds meaning for expected_matrix_world_mm, matrix_tolerance_mm and canonical_view, but says nothing about pattern_uuid, group_name, view_ref, view_fingerprint, scene_token, budget_ms or request_id.

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 specific verb and resource: send one screen-relative Qt arrow press/release and read both scene exports. It also clarifies a scope boundary -- the optional matrix 'does not select a direction or step size' -- which separates it from the translate/step siblings in behavior even though none is named.

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?

No statement of when to use this versus alternatives such as world_grid_step_translate_axis or world_adapter_gizmo_drag, and no when-not guidance. The only conditional hint is 'Pass canonical_view to verify the world axes immediately before input', which is parameter guidance rather than tool-selection guidance.

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