Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

world_frame_calibrate_outline

Fit a selected outline to its retained world OBJ and validate separate edges to calibrate world-frame alignment in Marvelous Designer scenes.

Instructions

Fit the selected outline against its retained world OBJ and validate separate edges.

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": {
      "frame_request_id": "<frame_request_id>",
      "scene_token": "<scene_token>",
      "focal_seed_px": "<focal_seed_px>"
    },
    "name": "world_frame_calibrate_outline"
  }
}

Input Schema

NameRequiredDescriptionDefault
scene_tokenYes
focal_seed_pxYes
frame_request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, yet it says nothing about whether calibration mutates state, what permissions are required, whether validation is read-only, or what happens to the existing outline on failure. "Retained world OBJ" implies stored state but does not clarify side effects or reversibility. This is a minimal behavioral sketch, not transparent enough for a likely mutation/calibration operation.

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 a single short sentence with no filler, so it is concise and front-loaded with the action. However, it is so terse that the unexplained jargon ("retained world OBJ", "separate edges") reduces clarity rather than earning its place. The structure is efficient but under-explanatory for the complexity of a three-parameter calibration tool.

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?

Given three required parameters, no output schema, no annotations, and 0% schema coverage, the description should explain prerequisites, side effects, and return characteristics. Instead it gives only a single jargon-laden sentence and omits any operational context. An agent would have to guess at essential details before calling the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All three required parameters (frame_request_id, scene_token, focal_seed_px) have 0% schema description coverage, and the description never mentions any of them. It adds no meaning about what a "frame request" is, how scene_token should be sourced, or how focal_seed_px influences the fit. With zero compensation for the coverage gap, parameter semantics are effectively undocumented.

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 provides two specific verbs ("Fit" and "validate") and references particular resources ("selected outline", "retained world OBJ", "separate edges"). However, these are undefined domain terms, so an agent cannot confidently tell what a "retained world OBJ" is or how this differs from siblings like world_frame_observe_rings or world_frame_capture. The purpose is more specific than a tautology but still vague enough to leave material ambiguity.

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 when-to-use guidance, no indication of prerequisites (e.g., must an outline already be selected?), and no named alternatives or exclusion conditions. The agent is left to infer entirely from the tool name and sibling list whether this is the right calibration step. This is no guidance at all beyond the bare action.

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