Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

scene_adapter_cut_selected

Triggers one 2D cut-pattern action on a fresh Qt selection in Edit Pattern mode and returns only the action result; native line identity and partitioning are not verified.

Instructions

Trigger only actionCutPattern2D once in Edit Pattern mode with one fresh public Qt selection.

This proves action return only, never native line identity or a correct partition. Domain selection and native after-readback are caller/core obligations; partial/unknown is not retried.

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": {
      "view_ref": "<view_ref>",
      "view_fingerprint": "<view_fingerprint>",
      "selection_fingerprint": "<selection_fingerprint>",
      "scene_token": "<scene_token>",
      "request_id": "<request_id>"
    },
    "name": "scene_adapter_cut_selected"
  }
}

Input Schema

NameRequiredDescriptionDefault
view_refYes
budget_msNo
request_idYes
scene_tokenYes
view_fingerprintYes
selection_fingerprintYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavioral traits beyond structured fields: the guarantee is limited to action return, never native line identity or a correct partition, and partial/unknown outcomes are not retried. What is missing is failure behavior (what an error or partial result looks like), side effects on the scene, and the meaning/limits of budget_ms, which matter for a mutation-style trigger.

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 sentences with the single-shot constraint front-loaded and no filler; each sentence adds a distinct claim (what fires, what it does not prove, who owns the rest). It is compressed to the point of opacity, but nothing is redundant.

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?

This is a complex, six-parameter, five-required trigger with no annotations and no output schema, yet the description explains none of the parameters and gives no return or failure detail. The stated proof boundary is valuable but insufficient for an agent to call it correctly on the first attempt.

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 six parameters, so the schema supplies only types and names. The description gestures at a 'fresh public Qt selection' and 'scene' but does not explain view_ref, view_fingerprint, selection_fingerprint, scene_token, request_id, or budget_ms, so the agent must guess at freshness/token semantics — the most failure-prone part of the call.

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

Purpose4/5

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

The description names a specific action (actionCutPattern2D) and a specific mode precondition (Edit Pattern mode) with a single fresh public Qt selection, which is far more precise than a restatement of the name. It is dense with internal jargon ('public Qt selection', 'native line identity'), so an agent without domain context gets the shape but not the full meaning, and it never contrasts itself directly with nearby siblings such as cut_qt_execute_selected.

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 heavily narrowed by 'only ... once' and by the statement that domain selection and native after-readback are caller/core obligations, which tells the agent what it must arrange beforehand. However, no alternative tool is named and no explicit when-not condition is stated, so the agent must infer routing from context rather than from the text.

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