Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

cloth_recover_positions

Restore the original mode after a failed MeshBox entry by supplying the unresolved Cloth position request and scene token; recovery skips the vertex edit and quarantines the failed frame bridge.

Instructions

Restore the original mode after a verified MeshBox entry failed before selection.

Supply the original unresolved Cloth position request and its current scene token. Recovery never repeats the vertex edit and the failed frame bridge remains quarantined.

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

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.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose meaningful behavior: recovery 'never repeats the vertex edit' and the failed frame bridge 'remains quarantined', which tells the agent this is a safe, non-destructive rollback rather than a retry. It omits what state is restored, whether partial state can remain, and what the call returns, so disclosure is partial rather than complete.

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?

Three short sentences with the triggering condition front-loaded, then the required inputs, then the safety guarantee. There is little waste, though the jargon density and the unqualified 'original mode' phrase cost some readability.

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 three-required-parameter mutation-adjacent recovery tool with no annotations and no output schema, the description is thin: it does not define blocked_request_id, explain how to verify the failed entry, or say what the restored result looks like. The agent would need to guess at one mandatory input and at success criteria before calling.

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%, so the description must give meaning to all three required parameters. It loosely maps 'the original unresolved Cloth position request' to request_id and 'current scene token' to scene_token, but blocked_request_id is never explained, nor is where to obtain any of these values, leaving a mandatory parameter undefined in both schema and prose.

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 frames this as restoring 'the original mode' after a verified MeshBox entry failed before selection, and the name says positions; the 'mode' vs. 'positions' framing leaves the actual action somewhat ambiguous. It is clearly a recovery/rollback operation tied to a failed Cloth position request, but no sibling is named or contrasted, and heavy jargon ('MeshBox entry', 'frame bridge') limits how concretely an agent can pin the purpose.

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?

Usage is implied by the precondition 'after a verified MeshBox entry failed before selection', which tells the agent the failure scenario that triggers this tool. However, it never states the negative case, prerequisites for verifying the failure, or alternatives such as the other recovery/reconcile siblings (cloth_reconcile_rest_archive, md_recover_*), so the agent must infer when this is preferred.

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