Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

md_reconcile_property_operation

Reconciles a returned Simulation Properties command after a failed diagnostic read, preserving its original outcome without re-triggering it when page and native/runtime scope remain unchanged.

Instructions

Observe a known-returned Simulation Properties command after its diagnostic read failed. Requires a complete current page and unchanged original native/runtime scope. Keeps the original outcome and never triggers the command again.

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

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

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

With no annotations, the description must carry the behavioral burden, and it does disclose key invariants: the tool keeps the original outcome and never triggers the command again. It still omits what happens when the required page or scope conditions are unmet, what the tool returns, and whether any side effects occur beyond observation.

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 description is short and front-loads the scenario, then moves to preconditions and the non-retrigger invariant. It is concise, though the dense jargon makes it harder to parse than a more plainly structured definition would be.

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 reconcile operation with three opaque required parameters, no annotations, and no output schema, the description leaves major operational gaps. It states preconditions and one key invariant but does not make the tool safely invocable without outside knowledge of the parameter meanings and failure behavior.

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?

All three parameters are required, have 0% schema description coverage, and are not explained in the description. Terms like “complete current page” and “original native/runtime scope” hint at scene_token or request data, but the description never clarifies request_id versus blocked_request_id or how any identifier should be supplied.

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 a specific action and domain object: observing a known-returned Simulation Properties command after a diagnostic read failure. However, it does not clearly explain what “reconcile” means in practice, nor does it differentiate the tool from nearby siblings such as md_reconcile_world_camera or md_recover_curve_operation.

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?

It gives a narrow trigger condition, “after its diagnostic read failed,” but provides no explicit when-to-use guidance, no alternatives, and no when-not conditions. An agent still has to infer when this tool is preferable to the other reconcile or recovery tools.

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