Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

world_frame_observe_rings

Read ring contour candidates in a verified Marvelous Designer frame, using physical PNG pixel coordinates to constrain observation to a specified ROI.

Instructions

Read ring contour candidates in a verified frame. ROI uses physical PNG pixels.

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>"
    },
    "name": "world_frame_observe_rings"
  }
}

Input Schema

NameRequiredDescriptionDefault
roi_pxNo
scene_tokenYes
frame_request_idYes

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?

With no annotations, the description carries the full burden. It implies a read-only observation but never says so explicitly, never states whether a frame must be captured/calibrated first, whether results are cached or recomputed, or what happens if the frame is not verified. Only the ROI pixel-coordinate convention is disclosed.

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 short sentences, front-loaded with the core action and with zero filler. It is terse to the point of being cryptic, but no sentence is wasted.

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?

A three-parameter read tool with no annotations, no output schema, and no schema descriptions needs the description to explain both inputs and the shape of the returned contour candidates. The description omits the return structure entirely and leaves two required parameters undocumented.

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 three parameters. It clarifies that roi_px is expressed in physical PNG pixels (useful), but says nothing about the expected array layout, and leaves scene_token and frame_request_id entirely unexplained despite both being required.

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?

"Read ring contour candidates" names a verb and a resource, so the broad intent is clear, but "ring contour candidates" and "verified frame" are unexplained domain jargon. Nothing in the description distinguishes this from siblings like world_frame_calibrate_outline or world_frame_capture.

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 prerequisites stated beyond the passing mention of a "verified frame", and no indication of when an agent should pick this over the capture or calibrate siblings. The agent must infer selection from the name alone.

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