Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

cloth_read_scene_positions

Reads a bounded sample of scene-wide XYZ cloth positions for diagnostics, returning a count and hash while flagging unverified native units/order and no editable vertex references.

Instructions

Diagnostic scene-wide XYZ getter: native units/order unverified, no editable owner/vertex references. Returns a bounded sample and count/hash.

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

Input Schema

NameRequiredDescriptionDefault
scene_tokenNo
sample_countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does disclose real behavioral traits: it is read-only in effect, returns only a bounded sample rather than full data, returns count/hash, and the units/order are unverified. It omits any note on permissions, rate limits, or failure modes, keeping it below a 5.

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 dense sentence, front-loaded with the tool's identity and immediately followed by the two caveats an agent most needs. Nothing is wasted, though the colon-and-clause packing makes it slightly harder to parse than a two-sentence split would be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-optional-parameter read tool with no output schema, the definition covers the essentials: what it returns (bounded sample plus count/hash), what it does not return (editable references), and the trustworthiness of the data. The remaining gap is parameter-level detail, which the schema's 0% coverage leaves unfilled.

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 description coverage is 0%, so the description must compensate. It conveys that the result is sampled and bounded, which maps to sample_count, and that the scope is scene-wide, which maps to scene_token, but neither parameter is named, and the null default for scene_token and the default of 4 for sample_count are 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 description states a specific verb and resource (scene-wide XYZ getter) and qualifies it as diagnostic, with the key limitation 'no editable owner/vertex references,' which separates it from editable position tools like cloth_get_positions. It falls short of naming a sibling outright, so an agent must infer the alternative from the phrasing.

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?

'Diagnostic' plus 'native units/order unverified' and 'no editable owner/vertex references' tells the agent when this is appropriate (inspection, not editing) and quietly warns against using its output for authoring. However, no alternative tool is named and no explicit when-not rule is given, so guidance is implied rather than stated.

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