Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

world_gizmo_scale_recover_pair

Recovers a blocked native scale operation by restoring verified pending inverse transforms in the original view, using request and scene tokens to identify the held phase.

Instructions

Observe the held native scale phase and restore its verified pending inverses in the original view.

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_gizmo_scale_recover_pair"
  }
}

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 disclose behavior, but it does not explain whether this mutates state, what "restore" changes, whether the operation is reversible, or what preconditions must hold. It hints at observing a held phase and restoring verified inverses, but leaves side effects and failure behavior unclear.

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?

It is a single sentence with no filler, so it is appropriately sized. However, it is jargon-dense and does not front-load the recovery action or the required parameters, reducing clarity despite being short.

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 a tool with three required string parameters, no annotations, and no output schema, the definition is too sparse. It does not explain prerequisites, expected effects, return behavior, or how the identifiers relate to the recovery operation.

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 does not mention or explain request_id, scene_token, or blocked_request_id. The required identifiers are undocumented in both the schema and the description, leaving their roles entirely unclear.

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 names an observe-and-restore operation tied to a held native scale phase, so it is more than a tautology. However, phrases like "verified pending inverses" and "original view" are opaque, and it never clearly defines what the "pair" is or how this differs from sibling inspect/prove tools.

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?

There is no explicit guidance on when to use this tool, when not to use it, or which sibling it replaces. The only implied usage is that it applies to a held scale phase with pending inverses, which an agent must infer from jargon.

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