Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

world_grid_step_recover_axis

Restore the original Grid field for an eligible same-process request without moving geometry, enabling recovery of axis state after a blocked operation.

Instructions

Restore the original Grid field for an eligible same-process request without moving geometry.

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": "world_grid_step_recover_axis"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYes
scene_tokenYes
blocked_request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses only that geometry is not moved; it says nothing about permissions, reversibility, side effects, what happens to the current Grid field, or what an 'eligible' request requires.

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 single sentence is front-loaded with the verb and contains no filler. It is appropriately sized, though its brevity is partly due to under-specification rather than efficient communication.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, three undocumented required parameters, and a mutation operation, the description is far too sparse. It does not explain eligible conditions, failure behavior, return values, or parameter roles.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description never mentions request_id, scene_token, or blocked_request_id. It adds no meaning beyond the bare parameter names, so an agent gets no guidance on what these IDs represent or how they relate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Restore') and identifies the target as 'the original Grid field,' and the clause 'without moving geometry' distinguishes it from translate-style siblings such as world_grid_step_translate_axis. However, 'Grid field' and 'eligible same-process request' are undefined domain terms, leaving the actual purpose vague.

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?

The only usage condition is the circular phrase 'for an eligible same-process request,' which does not explain what makes a request eligible or when to choose this over siblings like world_grid_step_inspect or world_gizmo_scale_recover_pair. No alternatives or exclusions are named.

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