Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

rest_open_simulation_properties

Opens the enabled Simulation Properties action once and verifies the current native 2D/runtime scope while keeping Marvelous Designer minimized.

Instructions

Trigger only the existing enabled/noncheckable Simulation Properties action once.

Keeps MD minimized; reads the resulting page and verifies current native 2D/runtime scope. No simulation, menus, arbitrary action, show/raise/activate, Rest write or old-page restore. Handler faults/modal behavior cannot be contained; unknown is not retried.

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

Input Schema

NameRequiredDescriptionDefault
budget_msNo
request_idYes
scene_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are present, so the description carries the full burden. It does disclose useful behavior: Minimizing MD, reading the resulting page and verifying scope, handler faults and modal behavior being uncontainable, and unknowns not being retried. It does not say what permissions or GUI session state are required, or what the caller should do if the action is missing or disabled.

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?

It is short and front-loads the action and its constraints, with no filler sentences. The telegraphic, jargon-heavy phrasing ('Keeps MD minimized', 'noncheckable') costs some readability for an outside agent but not much length.

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?

There is no output schema and no annotations, so the description must cover everything, and it covers behavior and scope well. It falls short on the three input parameters and on what a successful call actually returns or how failures surface.

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 three parameters (scene_token, request_id, budget_ms), and the description never mentions any of them. An agent must guess what scene_token scopes, what request_id is used for (idempotency?), and what budget_ms defaults or bounds mean.

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 first line names a specific verb and resource: trigger the existing enabled/noncheckable Simulation Properties action, once. That is concrete enough to distinguish the tool from the other rest_* siblings, but terms like 'noncheckable' and 'native 2D/runtime scope' are internal jargon, so the exact effect is only partly clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit exclusions: no simulation, no menus, no arbitrary action, no show/raise/activate, no Rest write, no old-page restore. That tells an agent much about when not to call it, but it never names an alternative sibling to use in those cases, so routing is inferred rather than stated.

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