Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

scene_adapter_inspect_2d

Inspect 2D view/tool references, metadata, and zoom/fit/frame action declarations without invoking methods, so you can review scene state before acting.

Instructions

Read current 2D view/tool refs, public metadata and zoom/fit/frame action declarations.

No method/action is invoked. This does not establish native-mm mappings or handler callability.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "scene_adapter_inspect_2d"
  }
}

Input Schema

NameRequiredDescriptionDefault
budget_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/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 meaningful work: it declares the call is non-mutating ('No method/action is invoked') and sets hard limits on the data ('does not establish native-mm mappings or handler callability'), which prevents over-trusting the result. Gaps remain: nothing about staleness of refs, whether a host session must exist, or failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with what is read, followed immediately by the two most important limitations. No filler, no restatement of the name, and every clause carries information an agent needs.

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?

There is no output schema and no annotations, so the description is the only source of return-shape information — and it only lists categories (refs, metadata, action declarations) without indicating structure, fields, or depth. For a pure inspection tool that is probably sufficient to decide whether to call it, but not to use the result confidently.

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% for the single parameter budget_ms, and the description says nothing about it — no units beyond the name, no statement of what happens when the budget elapses or what is returned truncated. The default value (750) softens the impact, but the description does not compensate for the coverage gap.

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 resource: read the current 2D view/tool refs, public metadata, and zoom/fit/frame action declarations. An agent can tell this is a read-only state inspection rather than a manipulation. It does not explicitly name or contrast with siblings like scene_adapter_runtime_capabilities or world_adapter_inspect_3d, so differentiation is only implied by the '2D' scope.

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: 'No method/action is invoked' plus the caveats tell the agent this is a pre-flight reconnaissance call, not an action. However, there is no explicit when-to-use, no pointer to alternatives when inspection is insufficient, and no statement of prerequisites (e.g., a live scene/host session).

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