Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

mesh_read_scene

Exports a fresh scene-wide garment OBJ in world millimeters; use summary-only mode to compare canonical digests of positions, UVs, normals, face indices, and labels without returning arrays.

Instructions

Fresh scene-wide garment OBJ export in world mm. Use summary_only to compare the canonical digest of positions, UVs, normals, face indices, and labels without returning arrays. The full OBJ remains available at its verified asset path. Vertex references require the full snapshot.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mesh_read_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
scene_tokenNo
summary_onlyNo
vertex_indicesNo

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, the description must carry the behavioral burden. It discloses that the export is fresh, scene-wide, in world mm, that a digest covers positions/UVs/normals/face indices/labels, and that the full OBJ remains at a verified asset path, but it omits read-only/safety implications, permissions, and the concrete return shape.

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?

The description is four tight sentences and front-loads the core export behavior before explaining the summary mode and vertex-reference constraint. It is appropriately sized, with only minor jargon such as 'verified asset path' that could be clearer.

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 three-parameter tool with no annotations and no output schema, the description covers the export modes and digest behavior reasonably. However, it does not explain scene_token or what a normal full export call returns, leaving important context gaps.

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 should compensate. It explains summary_only and implies that vertex_indices require the full snapshot, but scene_token is never described, leaving a key parameter undocumented.

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 states a specific action and resource: a fresh scene-wide garment OBJ export in world millimeters. It is clear what the tool produces, though it does not explicitly differentiate itself from siblings such as mesh_read_group.

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?

It gives concrete mode guidance: use summary_only to compare digests without arrays, and vertex references require the full snapshot. It does not explain when to choose this tool over sibling read tools or when not to use it.

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