Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

cloth_reconcile_rest_archive

Observe a closed native Rest action with a fresh archive and complete current OBJ, then release its lease only after the same scene and owner are independently confirmed without sending another Rest action.

Instructions

Observe the original closed native Rest action with a fresh archive and complete current OBJ.

Retains its original outcome and releases its lease only after the same scene and owner have been independently observed. Sends no second Rest button action.

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

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

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

With no annotations supplied, the description carries the full burden, but it does disclose real behavioral traits: it retains the original outcome, releases the lease only after independent observation of the same scene and owner, and issues no second Rest action. Still missing are what the "fresh archive" writes or destroys, failure modes, and whether the operation is idempotent or retry-safe.

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?

The text is short and the action is front-loaded in the first clause, so it earns points for length discipline. But dense jargon and an awkward mid-sentence line break reduce readability, and no sentence defines the opaque terms.

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 reconciliation tool with leases, no annotations, and no output schema, the description should explain inputs and return/outcome semantics. It covers some lease behavior but leaves parameter meanings and response expectations entirely unaddressed.

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 all three required parameters, so the description must compensate. It only obliquely references scene and owner ("the same scene and owner have been independently observed"), leaving request_id versus blocked_request_id entirely unexplained.

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 states an action ("Observe the original closed native Rest action with a fresh archive") and mentions retaining an outcome, which hints at a reconcile/archive operation. However, key terms like "closed native Rest action" and "complete current OBJ" are domain jargon that don't map to a plainly stated verb+resource, so an agent can't easily distinguish this from siblings such as cloth_rest_shape or cloth_recover_positions.

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 guidance on when to use this tool versus the many cloth_* and md_reconcile_* siblings, and no preconditions or exclusions are stated. The only routing-like statement is negative ("Sends no second Rest button action"), which describes behavior rather than when-to-use.

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