Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

cut_along_internal_shape

Cuts once along an existing whole internal shape using cut_inspect references, avoiding new lines or index retries; requires explicit 2D partition request when surface preservation is off.

Instructions

Cut once along an existing whole internal shape, never create a line or retry indices. Use refs from cut_inspect. Coordinates/tolerances are 2D mm. Default 3D/Rest/UV preservation is unsupported; explicitly false requests only native 2D partition evidence. Cut & Sew also reports unverified seam readback.

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": {
      "pattern_uuid": "<pattern_uuid>",
      "shape_uuid": "<shape_uuid>",
      "topology_fingerprint": "<topology_fingerprint>",
      "scene_token": "<scene_token>"
    },
    "name": "cut_along_internal_shape"
  }
}

Input Schema

NameRequiredDescriptionDefault
line_uuidNo
request_idNo
shape_uuidYes
cut_and_sewNo
scene_tokenYes
pattern_uuidYes
topology_fingerprintYes
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 disclose that this is a single-attempt mutation, that non-2D preservation is unsupported, and that Cut & Sew returns unverified seam readback — genuinely useful caveats. It omits the safety profile (destructive/irreversible nature of the cut, failure behavior, idempotency of request_id, stale-token rejection), leaving meaningful gaps 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?

Four dense sentences, front-loaded with the action and its hard constraint, and each sentence adds new information rather than restating the name. The jargon ('native 2D partition evidence', 'unverified seam readback') is terse but informative.

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?

For an 8-parameter mutation tool with no annotations and no output schema, the description covers behavior, units, and key caveats reasonably well. The remaining gap is the required identifier and concurrency parameters (scene_token, topology_fingerprint, request_id), whose purpose an agent must guess.

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 coverage is 0% across 8 parameters, so the description must compensate. It clarifies units (2D mm), the refs source for shape/line identifiers via cut_inspect, and the semantics of two optional flags (cut_and_sew readback caveat, require_surface_preservation needing explicit false despite the schema default of true), but leaves pattern_uuid, scene_token, topology_fingerprint and request_id entirely unexplained.

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 and resource ('Cut once along an existing whole internal shape') and immediately delimits scope ('never create a line'), which separates it from line-creation and selection tools. It does not explicitly contrast with the other cut execution siblings (cut_qt_execute_selected, scene_adapter_cut_selected), so differentiation is only partial.

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?

'Use refs from cut_inspect' gives a concrete prerequisite and implied alternative for obtaining identifiers, and 'Cut once ... never retry indices' states a usage constraint. However, there is no explicit when-to-use/when-not guidance against the other cut-execution siblings, so the agent must infer selection criteria.

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