Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

md_reconcile_world_rotation

Reconciles a blocked world-rotation request by reading fresh geometry and assignments and releasing only the original matching lease; check operation status first after a timeout.

Instructions

Observe a held closed rotation with fresh geometry and assignment readbacks.

Releases only the original matching lease. The original mutation outcome remains recorded and no further drag, offset setter or project reload runs. Check md_operation_status first when the original call timed out.

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": {
      "blocked_request_id": "<blocked_request_id>",
      "request_id": "<request_id>",
      "scene_token": "<scene_token>"
    },
    "name": "md_reconcile_world_rotation"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYes
scene_tokenYes
blocked_request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/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 add real value: it discloses that only the original matching lease is released, that the prior mutation outcome stays recorded, and that no further mutation or reload occurs. It says nothing about permissions, failure modes when request_id or scene_token are stale, or what 'fresh geometry and assignment readbacks' actually yields to the caller.

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 short sentences, front-loaded with the action and followed by side-effect constraints and the prerequisite check; nothing is redundant. Some phrasing ('held closed rotation', 'assignment readbacks') is dense domain jargon that costs a beat of comprehension, but the structure is sound.

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 reconciliation/verification tool with no output schema and no annotations, the description should say what the observation produces and how the caller should interpret a mismatch. It covers side effects and the prerequisite check well but leaves return semantics and the three required identifiers unexplained, so an agent could invoke it but might not interpret the result correctly.

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% for three required parameters (request_id, scene_token, blocked_request_id), and the description supplies no meaning for any of them. The names hint at request correlation and a scene handle, but the critical relationship — that blocked_request_id must match the original lease while request_id identifies the new call — is left entirely to inference.

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 description names a specific action and object: re-observing a held/closed world rotation with fresh geometry and assignment readbacks, and releasing the matching lease. The resource ('rotation') plus the readback/lease language separates it from siblings such as md_reconcile_world_camera and world_adapter_gizmo_drag. It stops short of a plain-language statement of what the tool returns, so it is clear but not effortless.

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?

It gives a concrete precondition — 'Check md_operation_status first when the original call timed out' — and rules out follow-on actions ('no further drag, offset setter or project reload runs'), which implicitly defines when to use this instead of re-running a mutation. There is no explicit statement of when not to call it or of what the caller should do if the lease no longer matches.

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