Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

world_adapter_read_camera

Reads CMT and CPT camera data from the same live 3D viewport and scene by scene token, enabling clients to inspect the current camera state.

Instructions

Read current CMT and CPT camera data tied to the same live 3D viewport and scene.

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": {
      "scene_token": "<scene_token>"
    },
    "name": "world_adapter_read_camera"
  }
}

Input Schema

NameRequiredDescriptionDefault
scene_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies a read-only snapshot tied to a live viewport and scene, which is useful context, but it never states what happens if no live viewport exists, whether the data is current or cached, or what permissions/session state are needed.

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?

One front-loaded sentence with no filler, but its brevity comes partly from unexplained acronyms rather than genuine economy of expression.

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 live-viewport read tool with an undocumented required token and no output schema, the description leaves too much open: return shape, acronym meanings, and failure conditions are all unaddressed. It is broadly complete only in the sense of naming what is read.

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 coverage is 0% and the single required parameter scene_token is never mentioned in the description. The description does not explain that scene_token binds the read to a particular scene, so it fails to compensate for the schema gap.

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 verb 'Read' and resource 'camera data' are specific enough, but 'CMT and CPT' are unexplained acronyms an agent may not resolve, and nothing distinguishes this from siblings such as md_reconcile_world_camera or world_adapter_inspect_3d. The phrase 'same live 3D viewport and scene' hints at scope but is ambiguous about what 'same' refers to.

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 statement of when to call this versus the camera-related or inspection siblings, no preconditions beyond an implied live scene, and no exclusions. The agent must infer usage entirely from the tool name.

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