Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

mesh_read_pattern

Check whether UUID-filtered pattern reads are supported and surface unbound export/group diagnostics; returns UNSUPPORTED with no mesh or vertex references.

Instructions

Diagnostic UUID-filter request. Current SDK can ignore patternList despite typed readback: returns UNSUPPORTED plus actual unbound export/group diagnostics, no UUID mesh or vertex refs. Use mesh_read_scene or an explicit OBJ-label mesh_read_group.

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": "mesh_read_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
scene_tokenNo
pattern_uuidYes
vertex_indicesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 behavioral burden, and it does disclose genuinely useful traits: the SDK may ignore patternList, the response returns UNSUPPORTED, and it contains "no UUID mesh or vertex refs." That is real failure-mode transparency, but it omits whether the call is a pure read, whether it errors or degrades gracefully, and what the diagnostics payload actually contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no filler, and the deprecation warning is front-loaded, which is good. However, the phrasing is dense with internal jargon ("typed readback," "unbound export/group diagnostics") that an unfamiliar agent must decode, reducing the clarity the brevity buys.

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 3-parameter tool with no annotations and no output schema, the definition adequately covers the surprising behavior (returns UNSUPPORTED, no mesh data) and where to go instead. It is incomplete on parameter meaning and on what the diagnostics actually report, which matters given the tool is explicitly framed as a diagnostic request.

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 coverage is 0%, so the description must explain all three parameters and does not: scene_token is never mentioned, pattern_uuid's meaning is only implied by "UUID-filter," and "patternList" is referenced as a concept but does not match a declared parameter name. Only vertex_indices is indirectly addressed via the note that no vertex refs are returned.

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?

"Diagnostic UUID-filter request" gestures at a UUID-keyed pattern read but uses an odd noun phrase instead of a clean verb+resource, and the rest of the sentence describes failure output rather than what the tool produces. The sibling references (mesh_read_scene, mesh_read_group) do help an agent place it, but the core purpose is obscured by jargon like "typed readback" and "unbound export/group diagnostics."

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

Usage Guidelines4/5

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

The description explicitly routes the agent elsewhere: "Use mesh_read_scene or an explicit OBJ-label mesh_read_group," which is a concrete when-to-use-instead rule naming two alternatives. It stops short of a 5 because it never states the condition under which this tool IS the right call (presumably pure diagnostics), leaving that to inference.

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