Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

mesh_read_group

Read one exact OBJ group label from a fresh scene export, compacting vertices, UVs, and normals while preserving bidirectional index maps and source face indices.

Instructions

Read one exact OBJ group label from a fresh scene export. Compacts vertices/UV/normals and preserves complete bidirectional export index maps and source face indices. Multi-group selected faces are rejected. Group refs are NOT pattern UUID, solver vertex, or native setter refs; other groups including topstitch are excluded by exact label.

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": {
      "group_name": "<group_name>"
    },
    "name": "mesh_read_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_nameYes
scene_tokenNo
vertex_indicesNo

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?

No annotations are supplied, so the description carries the full disclosure burden. It does useful work by stating that multi-group selected faces are rejected and by ruling out pattern UUID, solver vertex, and native setter refs as valid inputs, but it says nothing about return shape, error behavior, or what a 'fresh scene export' requires operationally.

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 with no filler, and the core action leads. The later sentences are jargon-heavy and read as a chain of caveats rather than a structured hierarchy, but nothing is redundant.

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?

With three parameters, no annotations, and no output schema, the description should explain more. It partially compensates by naming what is preserved in the output (bidirectional export index maps, source face indices), but leaves two of three parameters undefined and omits any statement of failure modes.

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%, so the description must carry all parameter meaning. It adds substantial semantics for group_name (exact OBJ label, not pattern UUID / solver vertex / native setter ref, topstitch excluded), but scene_token and especially vertex_indices are left 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 first sentence gives a specific verb and resource: read one exact OBJ group label from a fresh scene export, which is clearly narrower than a whole-scene or pattern read. However, it never names mesh_read_scene or mesh_read_pattern as the alternatives an agent should compare against, so sibling differentiation is implied rather than stated.

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?

Usage is only implied through constraints: the label must be exact, the export must be fresh, and multi-group selections are rejected. There is no explicit statement of when to choose this over mesh_read_scene or mesh_read_pattern, and no prerequisites around scene_token are given.

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