Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

cut_qt_execute_selected

Executes a selected Cut once from a validated reference, then verifies native partitions and optional 3D surface preservation.

Instructions

Consume one core-generated ref, revalidate, trigger selected Cut at most once and read native after.

The default also checks before/after exported 3D surface samples, area, orientation and non-target groups. Set require_surface_preservation=false for the native 2D partition check alone. The result identifies the exact verification scope.

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

Input Schema

NameRequiredDescriptionDefault
request_idYes
scene_tokenYes
selection_refYes
require_surface_preservationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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; it does useful work by disclosing the single-shot constraint ('at most once'), the revalidation gate, and the default verification checks. It never says whether the cut mutates the scene destructively, whether it can be undone, or how a failed revalidation is reported — significant omissions for a write operation.

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 tight sentences, front-loaded with the action, followed by the default behavior and the opt-out flag. No filler, though 'read native after' is compressed to the point of being cryptic and would benefit from one clarifying clause.

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?

There is no output schema, and the description only partially compensates by saying the result 'identifies the exact verification scope'. Given the tool performs an irreversible-looking geometry operation with three required opaque tokens, more detail on preconditions and failure outcomes is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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. It explains require_surface_preservation well (what it checks and how to disable it), but scene_token and request_id get no mention at all, and selection_ref is only alluded to as 'one core-generated ref'.

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 verb chain (consume ref, revalidate, trigger selected Cut, read native) on a specific resource, so an agent knows this is the execute step for a prepared Cut. It is weakened by domain jargon ('core-generated ref', 'read native') that obscures what is actually returned, but the core action is unambiguous.

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?

It implies sequencing (this runs after a ref has been generated elsewhere, presumably by cut_qt_prepare_line_selection) but never states that prerequisite or names an alternative. The one explicit routing decision given is the require_surface_preservation=false switch, which selects a lighter verification mode.

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