Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

scene_adapter_fit_all

Runs a fixed 2D Zoom Extents All in the current background viewport, then reads a fresh frame to verify which scene pieces are visible.

Instructions

Run the fixed 2D Zoom Extents All action in the current background viewport.

Read a fresh frame to verify which pieces are visible. No shortcut or physical input.

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

Input Schema

NameRequiredDescriptionDefault
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.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and delivers little. "No shortcut or physical input" hints that the action is dispatched without simulating keystrokes, but it never states whether the view change is persistent, what state is mutated, how the required tokens guard against stale scenes, or what happens on failure.

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?

Two short sentences with the action front-loaded and no filler. The second sentence ("Read a fresh frame to verify which pieces are visible") is terser than the rest and its meaning is not fully clear, but nothing is redundant.

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?

This is a viewport-mutating operation with no annotations, no output schema, and five undocumented parameters, yet the description spans only two sentences. It does not cover caller obligations around the token/fingerprint pair or what a successful fit returns, leaving material gaps for a mutation tool.

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 five parameters, four of them required opaque identifiers (view_ref, view_fingerprint, scene_token, request_id). The description explains none of them, and only the vague "current background viewport" phrase gestures at what view_ref might denote; budget_ms is entirely unexplained.

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 description names a concrete verb and action ("Run the fixed 2D Zoom Extents All action") and scopes it to "the current background viewport", so an agent knows this fits all scene content into view. It stops short of naming the sibling it is not (e.g. fit_selected), so the distinction between 'all' and 'selected' must be inferred from the name alone.

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 explicit when-to-use or when-not-to-use guidance. The phrase "in the current background viewport" implies context, but nothing tells the agent when to reach for this instead of scene_adapter_fit_selected, zoom_in_at, or a capture call.

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