Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

md_selected_patterns

Reads selected pattern UUIDs with native per-index flags and corroborating selected names so AI clients can identify the active patterns in a Marvelous Designer scene.

Instructions

Read selected pattern UUIDs using native per-index flags and corroborating selected names.

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

Input Schema

NameRequiredDescriptionDefault
scene_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations provided, the description must carry the full behavioral burden. It implies a read-only operation and mentions native per-index flags and corroborating selected names, but it does not disclose permissions, error behavior, or exactly what the caller receives.

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 definition is a single front-loaded sentence with no obvious filler. The phrase about native per-index flags and corroborating selected names is somewhat jargon-heavy, but the description remains compact.

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 optional parameter, no annotations, and no output schema, the description should explain the scene_token parameter and clarify the return shape. It partially implies the return values but leaves the parameter unexplained and gives no operational context.

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

Parameters1/5

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

The only parameter, scene_token, is not mentioned at all in the description, and the schema description coverage is 0%. The description does nothing to compensate for the undocumented parameter.

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 gives a specific verb and resource: it reads selected pattern UUIDs. It is clear enough to distinguish this read operation from the similarly named md_select_pattern, but it does not explicitly differentiate itself from siblings.

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 description states what the tool does but provides no guidance on when to use it versus alternatives such as md_select_pattern or md_scene. Usage is only implied by the name and brief phrasing.

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