Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

world_adapter_set_canonical_view

Set a canonical front, left, or quarter camera view and verify the camera basis, optionally fitting the garment to the same background 3D view.

Instructions

Set Front, Left or Quarter and verify the camera basis. Optionally fit the garment using the same background 3D view.

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

Input Schema

NameRequiredDescriptionDefault
viewYes
request_idYes
fit_garmentNo
scene_tokenYes

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?

No annotations are supplied, so the description carries the full behavioral burden. It implies a state mutation (camera basis is set) and a verification step, but says nothing about preconditions, whether the view is idempotent, what 'verify' means concretely, or what is returned, which is thin for a mutating camera tool with zero annotation coverage.

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 no filler, and the primary action is front-loaded before the optional secondary behavior. Nothing is redundant, though the second sentence is compressed to the point of ambiguity about how the fit relates to the view set.

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?

With three required parameters, no annotations, no output schema, and 0% schema coverage, the description should explain the required identifiers and what verification yields. It explains neither scene_token nor request_id and does not describe the outcome of the verify step, so an agent would be guessing on a required-parameter call.

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%, so the description must compensate for all four parameters. It gives meaning to view (the three orientations) and fit_garment (optional garment fit in the same background view), but scene_token and request_id are never explained, leaving two of four parameters with no documented purpose anywhere.

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 ('Set') plus the resource ('canonical view') and enumerates the three supported orientations (Front, Left, Quarter), so an agent can tell this apart from the read-side sibling world_adapter_read_camera. The secondary framing-verification and optional garment fit are also named, though 'canonical view' remains slightly jargon-dependent.

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 and no named alternative. 'Optionally fit the garment using the same background 3D view' hints at the fit_garment case but never tells the agent when that optional behavior should be enabled versus skipped, nor when to prefer the read/inspect camera siblings.

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