Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

rest_visible_contents_inspect

Reads the visible QWidget/PropertyEditorContents branch and prunes hidden widget pages, letting AI clients inspect only the contents currently visible in a Marvelous Designer scene.

Instructions

Read the actual visible QWidget/PropertyEditorContents branch, pruning all hidden widget pages.

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>"
    },
    "name": "rest_visible_contents_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
budget_msNo
scene_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, but it does disclose one genuinely behavioral fact: hidden widget pages are pruned, so the output is a filtered view rather than the raw tree. It says nothing about what a time budget does when exceeded, whether reads are side-effect free, or what the returned structure looks like.

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?

One sentence, front-loaded with the verb and resource, and the pruning qualifier is attached compactly. It is efficient, though the dense jargon phrasing ('QWidget/PropertyEditorContents branch') costs some immediate readability.

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 no annotations, no output schema, and zero parameter documentation, the definition is too thin. It does not explain the time-budget mechanism, the token lifecycle, or the shape of the pruned result, which are the things an agent most needs for correct invocation.

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 neither parameter is mentioned in the description. The 'rest_visible_contents_inspect' parameters, including the notable budget_ms with a 750ms default, are undocumented in either the schema or the prose, so an agent cannot tell how to size a budget or what scene_token represents.

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 specific verb ('Read') and a named resource ('visible QWidget/PropertyEditorContents branch'), so the operation is identifiable. However, it does not distinguish itself from plausibly overlapping siblings such as md_property_contents or rest_adapter_inspect_host_controls, and the technical jargon makes the scope harder to grasp than necessary.

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?

There is no statement of when to call this versus alternatives, no preconditions mentioned (beyond the implied need for a scene_token), and no exclusions. The agent must infer usage purely from the one-line purpose.

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