Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

cloth_vertex_context_inspect

Inspect current cloth vertex mode, Qt items, and SDK pattern selection for a scene without altering scene state.

Instructions

Observe current Cloth vertex mode, Qt items and SDK pattern selection.

Returns native vertex identity as unavailable and has zero input effects.

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": {
      "scene_token": "<scene_token>"
    },
    "name": "cloth_vertex_context_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
scene_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations at all, the description carries the full disclosure burden. It does add two useful facts ('zero input effects' and that native vertex identity is reported as unavailable), but it omits whether the call requires an active scene/selection, whether it errors outside Cloth mode, and what the returned mode/Qt/pattern fields look like.

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?

Two short sentences, front-loaded with the purpose and followed by the effect/return caveat; nothing is padded, though the second sentence mixes an output caveat with a side-effect claim.

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 an undocumented required token, the definition should do more: it should explain the scene_token and describe the shape of the returned mode/Qt/pattern data rather than only flagging that one field is unavailable.

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% and the single required parameter scene_token is not mentioned anywhere in the description, so its meaning, format, and how to obtain it are undocumented in both places.

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

Purpose3/5

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

The verb 'Observe' plus the resource list ('Cloth vertex mode, Qt items and SDK pattern selection') does say what is inspected, but the terms are domain jargon and no sibling is named or contrasted, so an agent cannot easily tell this apart from rest_simulation_context_inspect or cut_inspect.

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 statement of when to call this versus alternatives, no preconditions such as needing an active Cloth vertex mode, and no exclusions. The only implicit guidance is 'has zero input effects', which hints at a read-only probe.

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