Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

md_connect

Connects to the configured local Marvelous Designer listener and reads the active project, enabling scene inspection and editing without any window or input interaction.

Instructions

Connect to the configured local MD listener and read the active project. No window/input operation.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It does disclose one useful trait — it performs no window or input operations — but says nothing about whether the connection persists, what happens if already connected, failure modes, permissions, or whether any state is modified.

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 core action, with no filler. The trailing "No window/input operation" is terse to the point of being cryptic but does not waste space.

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?

For a zero-parameter tool with no output schema, the description leaves the return value undefined — "read the active project" gives no indication of what project data comes back or in what form. Given the absence of an output schema, the description should have covered the result shape; it is adequate but incomplete.

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 and the schema coverage is 100%, so there is nothing for the description to clarify. Baseline 4 applies for a parameterless tool.

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 gives a concrete verb pair ("connect" + "read the active project") and names the target ("configured local MD listener"), so the operation is identifiable. However, "MD" is never expanded, and the read-a-project aspect overlaps ambiguously with siblings such as md_project_open and md_scene without any stated distinction.

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?

The phrase "the configured local MD listener" implies this is a setup/attachment step, and "No window/input operation" implicitly distinguishes it from UI-driven siblings like canvas_gesture. But there is no explicit statement of when to call it versus md_capabilities or md_project_open, and no ordering or prerequisite guidance.

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