Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

world_adapter_read_group_binding

Reads the current SDK UUID/unique-name-to-OBJ group-label mapping, leaving extra groups unclassified so you can verify label-only bindings without input or DLLs.

Instructions

Read current SDK UUID/unique-name to exact OBJ group-label bijection, covering every current paper name with exclusive disjoint groups. Additional groups stay unclassified/protected. This proves labels only, not native mesh ownership or setter indices; exports once, no input or DLL required.

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>",
      "group_name": "<group_name>",
      "scene_token": "<scene_token>"
    },
    "name": "world_adapter_read_group_binding"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_nameYes
scene_tokenYes
pattern_uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does add real behavioral context: it discloses that extra groups remain unclassified/protected, that the call exports once, and that no input or DLL is required, plus a clear limit on what the mapping proves. What is missing is any statement about cost, permissions, or what the returned structure looks like, but the side-effect and scope profile is otherwise well covered.

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?

It is compact at two sentences with the main claim front-loaded and no filler, which is appropriate. However, terms like 'bijection' and 'exclusive disjoint groups' add density without adding clarity for an agent, trading brevity for opacity.

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?

The description explains the conceptual output and its limits, which is the strongest part, and no output schema exists so return values need not be spelled out. But for a tool with three mandatory, entirely undocumented parameters and no annotations, the definition leaves the agent unable to actually construct a valid call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All three required parameters (pattern_uuid, group_name, scene_token) have 0% schema description coverage, and the description never mentions any of them, so an agent has no basis for supplying correct values. With low coverage the description was obligated to compensate and does not.

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 description names a specific operation ('Read current SDK UUID/unique-name to exact OBJ group-label bijection'), so the resource and action are identifiable, but the wording is heavy with unexplained jargon ('bijection', 'paper name', 'exclusive disjoint groups') that makes it hard to tell at a glance how it differs from a sibling like mesh_read_group. The core purpose is recoverable but requires interpretation.

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 a partial scope statement ('This proves labels only, not native mesh ownership or setter indices'), which tells the agent what the result does not establish, but there is no explicit when-to-use guidance and no named alternative among the many sibling read tools. The agent is left to infer selection criteria from the name alone.

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