Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

cut_inspect

Resolves a current UUID and inspects topology-bound shape and line references plus distinct child and ordinal namespaces in a scene, read-only.

Instructions

Resolve a current UUID and inspect topology-bound shape/line references and distinct child/ordinal namespaces. Read-only.

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_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
scene_tokenNo
pattern_uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the key safety trait ('Read-only') and hints that stale UUIDs are resolved to a current one. It says nothing about failure modes for invalid or stale UUIDs, permission requirements, or what the inspection returns. Adequate but thin for a zero-annotation tool.

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?

A single front-loaded sentence with no filler, and the read-only qualifier is placed at the end where it is easy to scan. It is efficient, though the compressed jargon ('child/ordinal namespaces') costs some readability.

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?

With no annotations, no output schema, and 0% parameter description coverage, the description leaves too much unspecified: the meaning of the returned namespaces, the role of scene_token, and error behavior are all absent. For a two-parameter inspection tool in a crowded sibling set, more context is needed.

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. It only implies that pattern_uuid should be a current UUID; the scene_token parameter is never mentioned, and no format or scoping semantics are given for either parameter.

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 (inspect) and a specific resource (topology-bound shape/line references and child/ordinal namespaces), plus the resolution of a current UUID. It is dense domain jargon, but an agent can tell it is a read-only topology inspection rather than a mutation. It does not distinguish itself from the sibling cut_qt_inspect, which is the main gap.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative among the many cut_* siblings. The only implied guidance is that a current UUID must be resolved first, which an agent must infer from the phrase 'Resolve a current UUID'.

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