Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

world_adapter_inspect_topstitch_assignments

Reads current SDK Topstitch assignments and verifies exact OBJ group labels, so you can confirm stitching targets before editing or recovering a scene.

Instructions

Read current SDK Topstitch assignments and corroborate exact OBJ group labels.

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": {
      "scene_token": "<scene_token>"
    },
    "name": "world_adapter_inspect_topstitch_assignments"
  }
}

Input Schema

NameRequiredDescriptionDefault
scene_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It implies a read-only inspection but does not disclose permissions, whether it mutates anything, what happens on invalid scene tokens, or what kind of evidence the corroboration returns.

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 a single compact sentence with no wasted wording and the read action is front-loaded. Its brevity is appropriate, though it comes at the cost of clarity around the corroboration step.

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?

For a tool with one undocumented required parameter, no annotations, and no output schema, the description is too sparse. It does not explain the required scene token, the return shape, or the meaning of Topstitch assignments and OBJ group labels.

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?

The only parameter, scene_token, has 0% schema description coverage and is never mentioned in the description. The description adds no meaning about what a scene token is, its format, or where to obtain one.

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 verb and resource: reading current SDK Topstitch assignments. However, "corroborate exact OBJ group labels" is opaque and does not clarify what corroboration means operationally, leaving the tool's purpose only partially clear.

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 no explicit guidance on when to use this tool, when not to use it, or which sibling inspection tools are alternatives. The read-oriented phrasing implies inspection usage, but no conditions or exclusions 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