Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

scene_adapter_zoom_in_at

Zooms a Marvelous Designer viewport at a given point using a pinned wheel after a fixed scene hover; requires fresh 2D refs and Edit Curve Point mode, then verify zoom independently.

Instructions

One fixed NoMod scene hover then a version-pinned viewport wheel.

Requires fresh current 2D refs and Edit Curve Point mode. No OS wheel, focus, configurable delta, loop or automatic retry. Dispatch is not proof of actual zoom, pivot, magnification or native preservation; track/read back independently.

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>",
      "point": "<point>",
      "scene_token": "<scene_token>",
      "request_id": "<request_id>"
    },
    "name": "scene_adapter_zoom_in_at"
  }
}

Input Schema

NameRequiredDescriptionDefault
pointYes
view_refYes
budget_msNo
request_idYes
scene_tokenYes
view_fingerprintYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and it does disclose real constraints: no OS wheel, no focus dependency, no configurable delta, no loop, no automatic retry, and the important caveat that dispatch is not proof of actual zoom so the result must be read back. That is meaningful behavioral context. It still omits failure/error semantics, idempotency expectations for request_id, and what budget_ms expiry does, which matter for a no-retry mutation of view state.

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?

Four short sentences, front-loaded with the mechanism and followed by preconditions and caveats; there is very little waste. The opening clause is dense jargon that takes a re-read to parse, which costs some clarity but not 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?

For a six-parameter, no-annotation, no-output-schema tool, the description supplies critical safety context (no retry, verify by read-back) but leaves parameter meanings and failure behavior unexplained. An agent can avoid the worst mistakes but cannot confidently construct the point/token/request_id arguments from the definition alone.

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 coverage is 0% across six parameters, so the description must compensate and it only partly does: 'fresh current 2D refs' loosely maps to view_ref/view_fingerprint and 'version-pinned' hints at fingerprint staleness checking. Nothing explains point, scene_token, request_id, or budget_ms (default 750), leaving half the contract undocumented in both schema and prose.

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 describes the mechanism ('One fixed NoMod scene hover then a version-pinned viewport wheel') rather than stating the goal outright; the actual action, zooming in at a point, is only inferable by combining it with the tool name. It never references the sibling scene_adapter_zoom_out_at or any other alternative, so nothing separates it from neighbors beyond the name.

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?

'Requires fresh current 2D refs and Edit Curve Point mode' is a genuine precondition for correct invocation, which is more than most definitions offer. However, it gives no routing guidance against siblings (zoom_out_at, fit_all, set_canonical_view) and no explicit statement of when this tool is the wrong choice.

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