Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

scene_adapter_set_tool

Sets or verifies exactly one supported current-owner 2D tool action—transform pattern, pattern edit, or edit curve point—in a Marvelous Designer scene.

Instructions

Set exactly one of three fixed current-owner 2D tool actions, or verify already-current.

At most one QAction trigger; no arbitrary name, input or implicit model write verification.

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": {
      "view_ref": "<view_ref>",
      "view_fingerprint": "<view_fingerprint>",
      "tool": "<tool>",
      "scene_token": "<scene_token>",
      "request_id": "<request_id>"
    },
    "name": "scene_adapter_set_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYes
view_refYes
budget_msNo
request_idYes
scene_tokenYes
view_fingerprintYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description usefully adds an upper bound of one QAction trigger and exclusions involving arbitrary names/input and implicit model-write verification. However, the final exclusion is grammatically ambiguous, and the description does not clarify whether an already-current call triggers nothing, what state may change, or how verification and failure are reported.

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 purpose is front-loaded and the second sentence compactly adds execution limits, with no filler. The dense jargon and ambiguous final comma-separated phrase reduce clarity, but the overall structure is efficient.

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 six-parameter tool with five required inputs, no annotations, and no output schema, too much invocation behavior remains implicit. Ownership, fingerprint and token requirements, budget behavior, verification results, and failure semantics are undocumented despite the useful trigger cap.

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?

Schema description coverage is 0%, and the description does not explain view_ref, view_fingerprint, scene_token, request_id, or budget_ms, nor the distinct meanings of the three enum values. Saying there are exactly three fixed actions largely restates the enum rather than compensating for the undocumented parameters.

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 opening sentence gives a concrete operation: setting one fixed 2D tool action for the current owner, with an already-current verification mode. It does not explicitly differentiate sibling scene operations, and "current-owner" is left unexplained.

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 fixed-action scope and "verify already-current" wording suggest constrained tool switching or idempotent confirmation, while arbitrary tool names are excluded. There is no guidance on ownership or freshness prerequisites, nor when to use another scene_adapter operation.

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