Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

cut_qt_inspect

Reads shape/line references and fresh PointInfo geometry for the current paper, returning IDs needed to prepare cut operations with scene token and topology fingerprint.

Instructions

Read shape/line references and fresh PointInfo geometry binding for the current paper.

Pass the returned shape_uuid and line_uuids with the scene token and topology fingerprint to prepare. export_shape_id and export_line_ids are diagnostic.

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>"
    },
    "name": "cut_qt_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
scene_tokenNo
pattern_uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations present, the description carries the full disclosure burden. It does useful work by naming the returned identifiers (shape_uuid, line_uuids, export_shape_id, export_line_ids) and flagging which are diagnostic versus actionable, but it never states that the operation is non-mutating, what permissions or runtime state it requires, or what happens if the scene token is stale.

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 short sentences, front-loaded with the purpose and followed by the hand-off contract. No filler, though the trailing 'export_shape_id and export_line_ids are diagnostic' note is terse to the point of ambiguity about what diagnostic implies for the caller.

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 a two-parameter read tool with no annotations and no output schema, the description usefully enumerates the return keys, which is more than most. The gaps are the unexplained required pattern_uuid and the orphan reference to a topology fingerprint, leaving the agent's input contract partly unresolved.

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%, so the description must compensate, and it largely does not. The required pattern_uuid parameter is never mentioned, scene_token is only obliquely referenced, and the description introduces a 'topology fingerprint' input that does not exist in the schema at all, which risks misleading the agent about what to supply.

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 gives a specific verb ('Read') and a concrete resource ('shape/line references and fresh PointInfo geometry binding'), which is enough to distinguish it from the mutating siblings like cut_qt_execute_selected and cut_qt_prepare_line_selection. It stops short of a 5 because terms such as 'PointInfo' and 'current paper' are domain jargon that an unfamiliar agent cannot resolve from the description alone.

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?

Sequencing guidance is implied but not explicit: 'Pass the returned ... to prepare' signals this is a prerequisite read step before a prepare call. However, the target tool is referred to only as 'prepare' rather than a concrete name, and there is no statement of when not to use this tool or what alternatives exist.

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