Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

rest_set_pinching_override

Sets only the visible Pinching Simulation Override checkbox to a requested value and reads it back, clicking once only when the value changes and returning the original UI state for restoration.

Instructions

Set only the currently visible Pinching Simulation Override checkbox and read it back.

Native batch keeps MD minimized. No simulation/brush/Update Rest/Reset Rest action. A changed value causes exactly one public checkbox click; a matching value causes none. Restore with the returned original_ui_value when this independent trial is finished. Unknown results must never be replayed automatically.

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": {
      "scene_token": "<scene_token>",
      "request_id": "<request_id>",
      "enabled": "<enabled>"
    },
    "name": "rest_set_pinching_override"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes
budget_msNo
request_idYes
scene_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and delivers real behavioral detail: one public checkbox click when the value changes, none when it matches, a restore value for reverting, and a hard rule that unknown results must never be replayed. It omits timeout/budget behavior and what a failed or partial click looks like, which keeps it from a 5.

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?

Short, front-loaded, and each line carries a constraint rather than filler. The line 'Native batch keeps MD minimized' is cryptic internal jargon that costs the reader without adding actionable guidance.

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

Completeness3/5

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

A state-mutating UI tool with no annotations, no output schema, and undocumented parameters needs more than this. It does supply the key return value (original_ui_value) and idempotency semantics, but parameter meaning and failure handling are missing.

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% across four parameters, so the description must compensate and largely does not. It implies the meaning of 'enabled' (changed vs matching value) but never explains scene_token, request_id (plausibly an idempotency/replay key, which matters given the replay warning), or budget_ms.

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

Purpose5/5

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

States a specific verb and a tightly scoped resource: 'Set only the currently visible Pinching Simulation Override checkbox and read it back.' The word 'only' plus the explicit exclusion list makes it distinguishable from inspection siblings such as rest_adapter_inspect_host_controls and rest_visible_contents_inspect even without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear when-not guidance ('No simulation/brush/Update Rest/Reset Rest action') and a lifecycle rule for finishing a trial and restoring with original_ui_value. It stops short of naming a concrete alternative tool for the excluded operations, so it is not a full 5.

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