Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

md_scene

Reads current Marvelous Designer project identity, paper UUIDs, input topology, quality, and scene token without loading fixtures, letting AI clients inspect scene state before editing.

Instructions

Read current project identity, paper UUIDs/input topology, quality and scene_token. No fixture loading.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 load; 'Read' plus 'No fixture loading' signals a non-mutating call that will not initialize fixtures, which is genuinely useful context. It does not state whether it fails when no project is open, whether results are cached, or what happens if topology is unresolved.

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?

Two short sentences, front-loaded with the verb and the returned payload, and the fixture caveat placed last as a qualifier. It is dense with domain jargon ('paper UUIDs/input topology') but no sentence is wasted.

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 no parameters and no output schema, the description is the only source for what comes back, and its list of fields is cryptic rather than explanatory ('input topology', 'quality' with no scale or meaning). It is minimally sufficient to identify the tool but leaves an agent guessing about the response shape.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate at the argument level. Baseline of 4 applies for a parameterless tool.

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 names a specific verb ('Read') and enumerates the resources returned: project identity, paper UUIDs/input topology, quality, and scene_token. This makes the tool's output scope concrete, though it never contrasts itself with siblings such as md_capabilities or mesh_read_scene, so an agent must infer which reader to pick.

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?

The only guidance-like statement is the trailing 'No fixture loading.', which is a side-effect disclaimer rather than a when-to-use rule. There is no indication of prerequisites (e.g., must a project be open via md_project_open first) or when to prefer this over md_capabilities.

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