Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

scene_adapter_zoom_out_at

Zooms out the current 2D viewport by one fixed wheel step in Edit Curve Point mode, then reads a fresh frame to verify the zoom without OS input or foreground activation.

Instructions

Apply one fixed outward wheel in Edit Curve Point mode on the current 2D viewport.

Uses the pinned adapter with no OS input or foreground activation. Read a fresh frame to verify the zoom.

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_out_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.2/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 does disclose useful behavior beyond the schema: it is a single fixed wheel step, it uses a pinned adapter, and it requires no OS input or foreground activation, i.e. it does not move the real cursor. It does not say whether the zoom is undoable, what state changes are committed, or what a success/failure response 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?

Three short sentences, front-loaded with the action and mode, then mechanism, then verification step. Nothing is padded, though the 'pinned adapter' phrasing is somewhat internal jargon rather than agent-facing guidance.

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?

Adequate on mechanism but thin overall for a tool with 6 parameters, 5 required, zero annotation coverage, and no output schema. Nothing explains the required tokens/fingerprint or what the call returns, which are the details most likely to cause a failed 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?

All six parameters have 0% schema description coverage and the description names none of them. The meaning of view_ref, view_fingerprint, scene_token, request_id, and budget_ms (a 750ms default) is left entirely unexplained, so an agent must guess at the token/fingerprint contract for what appears to be a guarded mutation.

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 mechanism: 'Apply one fixed outward wheel in Edit Curve Point mode on the current 2D viewport.' An agent can tell this is a discrete zoom-out step rather than a continuous gesture or a fit operation, though it never names scene_adapter_zoom_in_at as its counterpart.

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 precondition (Edit Curve Point mode, current 2D viewport) and the follow-up workflow ('Read a fresh frame to verify the zoom') are stated, which gives implied usage context. But there is no explicit when-not guidance and no named alternative such as zoom_in_at or fit_selected.

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