Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

md_project_save_copy

Save the current Marvelous Designer scene state to a new absolute .zprj filename, rejecting existing outputs; saving may change the active project path.

Instructions

Save current state to a new absolute .zprj filename; existing outputs are rejected. Saving can change the active project path.

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": {
      "path": "<path>",
      "request_id": "<request_id>",
      "scene_token": "<scene_token>"
    },
    "name": "md_project_save_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
request_idYes
scene_tokenYes

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, the description carries the behavioral burden and usefully discloses both non-overwrite behavior and the possible side effect of changing the active project path. It does not further explain when that path change occurs or describe failure and completion behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences front-load the operation, then state the overwrite restriction and active-path side effect. There is no filler or redundant wording.

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?

The core save-copy behavior and its most important side effect are adequately covered for a three-parameter mutation tool. Invocation guidance remains incomplete because two required parameters are opaque, and there is no output schema or description of success and error results to fill those 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?

The description substantially explains path by requiring an absolute, new, non-existing .zprj filename, compensating for part of the schema's 0% description coverage. However, the other two required parameters, request_id and scene_token, remain entirely unexplained, including their expected source or relationship to the current scene.

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 clearly states the action and resource: saving the current project state to a new absolute .zprj filename. The new-file requirement communicates save-as/copy behavior, although it does not explicitly contrast the tool with md_project_open or another save operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete selection guidance: use a new absolute .zprj path, and do not target an existing output because it will be rejected. It does not identify an alternative for replacing an existing file or state prerequisites such as having a current project.

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