Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

md_select_pattern

Selects a pattern by UUID while clearing any previous selection through the SDK. Useful for targeting one pattern before edits, without changing geometry or activating windows.

Instructions

Select exactly the current UUID's pattern, clearing previous selection through the SDK. Does not select a particular handle/line or change geometry; no OS input/window activation.

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

Input Schema

NameRequiredDescriptionDefault
request_idYes
scene_tokenYes
pattern_uuidYes
refresh_selectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the whole burden and does disclose one real side effect — previous selection is cleared — plus the fact the operation runs through the SDK rather than OS input. It says nothing about permissions, whether the change is undoable, or what happens when pattern_uuid is not in the active scene, which matters for a mutating selection tool.

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 front-loaded sentences, the affirmative behavior first and the exclusions second, with no filler. Slightly compressed phrasing ("the current UUID's pattern") costs a little clarity but nothing is wasted.

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?

A 4-parameter tool with 0% schema coverage, no annotations, and no output schema needs the description to explain the scene/request pairing and the refresh flag; the description covers purpose and exclusions but leaves all parameter behavior and error conditions unaddressed.

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% and all four parameters are bare titles. The description never mentions scene_token, request_id, or refresh_selection, so the meaning of the optional refresh_selection flag (presumably controlling whether the selection is re-asserted) is completely undocumented anywhere.

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 ("Select exactly the current UUID's pattern") and bounds the scope with explicit non-goals: no handle/line selection, no geometry change, no OS input. That tells an agent how it differs from gesture/transform siblings, though it doesn't name a sibling outright.

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 negative scoping ("Does not select a particular handle/line or change geometry; no OS input/window activation") implicitly steers an agent away from lower-level pointer/geometry tools, which is useful inferred guidance. However there is no explicit when-to-use condition or named alternative, so the routing is left to inference.

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