Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

md_reconcile_world_camera

Observes the current camera when a fixed-view request returns without verified readback, preserving the original UNKNOWN result tied to the scene and request.

Instructions

Observe the current camera after the original fixed-view request returned without verified readback.

The original view and scene identify the observation. The original UNKNOWN result is retained.

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": {
      "blocked_request_id": "<blocked_request_id>",
      "request_id": "<request_id>",
      "scene_token": "<scene_token>"
    },
    "name": "md_reconcile_world_camera"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYes
scene_tokenYes
blocked_request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose one meaningful trait — the original UNKNOWN result is retained — but it never clarifies whether the tool mutates world/scene state, whether it requires an active connection or open project, what it returns on success, or how failures surface. 'Observe' suggests a read but is never confirmed.

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

Conciseness3/5

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

The description is short and front-loads the action, which is good. But the middle sentence ('The original view and scene identify the observation') is vague to the point of not earning its place, while the genuinely informative disclosure about retaining the UNKNOWN result is buried last.

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?

For a three-required-parameter reconciliation tool with no annotations and no output schema, the description leaves too much unspecified: the meaning of blocked_request_id, the read/write nature of the call, prerequisites such as an open project or connected adapter, and the expected return. The description is far shorter than the tool's complexity warrants.

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 three required parameters with opaque names. The sentence 'The original view and scene identify the observation' loosely hints at scene_token and request_id, but blocked_request_id — arguably the most important parameter — is never explained, nor are the ID formats or where they come from.

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 names an action ('Observe the current camera') and a triggering situation ('after the original fixed-view request returned without verified readback'), which is more specific than a tautology. But the phrasing is domain jargon ('fixed-view request', 'verified readback') and never says plainly that this is a reconciliation/re-observe step or what it produces, so an agent must infer the core purpose.

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?

It supplies an implicit when-to-use condition: call this after a fixed-view request failed to return verified readback. That is real contextual guidance. However, it names no alternatives (the sibling md_reconcile_world_rotation is never referenced), gives no when-not-to-use, and does not say what to do with the result afterwards.

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