Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

md_project_open

Open an existing .zprj through explicit API options without dialogs; set replace_current to load into a nonempty scene without saving or overwriting the input file.

Instructions

Open an existing .zprj via explicit non-dialog API options. Replacing a nonempty scene requires replace_current. Never saves/overwrites the input file.

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_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
request_idYes
scene_tokenYes
replace_currentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/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. It does disclose one valuable side-effect boundary, that the input file is never saved or overwritten, but it says nothing about the in-memory scene being replaced, what happens to unsaved work, failure modes for a missing or invalid path, or the return value.

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 action and followed by the constraint. Slightly jargon-heavy phrasing ("explicit non-dialog API options") costs a little clarity, but nothing is padded.

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 four-parameter mutation-style tool with no annotations, no output schema and zero schema coverage, the description is thin. It leaves the two token parameters, the return shape, and error conditions for a new caller to guess.

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?

Schema description coverage is 0% across four parameters, so the description must do the explaining. It implies path is a file path and clarifies replace_current's condition, but request_id and scene_token are left entirely unexplained in both schema and description, leaving half the surface undocumented.

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?

States a specific verb and resource: opening an existing .zprj file. The qualifier "explicit non-dialog API options" signals this is a programmatic open rather than an interactive one, which helps distinguish it from a UI-driven open flow, though no sibling is named as a contrast.

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?

Includes one concrete conditional rule, that a nonempty scene requires replace_current, which is real usage guidance. However there is no statement of when to prefer this over alternatives, no prerequisites (does the path have to exist? must the scene be saved first?), and no exclusions.

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