Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

scene_adapter_fit_selected

Fits the current 2D view to exactly one SDK-selected pattern through a fixed native action, without OS input or window activation and without changing model coordinates.

Instructions

Fit the current 2D view to exactly one SDK-selected pattern through its fixed native action. No OS input or window activation; model coordinates are unchanged.

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_selected"
  }
}

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

B3.1/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 behavioral burden, and it does add real value by disclosing that there is no OS input injection or window activation and that model coordinates are left unchanged. It stops short of the failure contract, which matters most here: what occurs when the SDK selection is empty or has multiple patterns, and whether the call blocks until the view settles.

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 tight sentences with the scoping constraint front-loaded and the behavioral caveat second. The phrase 'through its fixed native action' is the only soft spot, being vague about what mechanism is actually invoked.

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?

The parameter set (view_fingerprint, scene_token, request_id, budget_ms) signals a staged validation and timeout contract on a mutating view operation, with no annotations and no output schema to lean on. Given that complexity the description is too thin, leaving the caller unable to construct a valid first call without trial and error.

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, so the description must compensate and does not. It never explains view_ref, view_fingerprint, scene_token, request_id, or budget_ms (default 750), leaving the fingerprint/token/request-id validation and idempotency contract entirely undocumented.

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 states a specific verb and resource: fit the current 2D view to exactly one SDK-selected pattern. The phrase 'exactly one SDK-selected pattern' implicitly carves out the difference from scene_adapter_fit_all, but the sibling is never named, so the distinction relies on the agent noticing 'fit_all' in the catalog.

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?

Usage is implied rather than stated: the agent can infer 'use when a single pattern is selected via the SDK', but there is no explicit when-not condition, no mention of what happens when zero or multiple patterns are selected, and no named alternative (scene_adapter_fit_all) to route to.

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