Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

scene_adapter_bezier_drag_unsnapped

Drags a Bezier curve between start and end points while temporarily disabling Snap to Pattern and Smart Guide, then restores both settings after the operation.

Instructions

Fixed four-phase Bezier batch with only Snap to Pattern/Smart Guide temporarily off.

The two unique current-owner actions are triggered only when needed, then restored by original state after paired Release (including failure cleanup). No arbitrary QAction/setting/key. Does not prove semantic hit or mm precision.

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_ref": "<view_ref>",
      "view_fingerprint": "<view_fingerprint>",
      "start": "<start>",
      "end": "<end>",
      "scene_token": "<scene_token>",
      "request_id": "<request_id>"
    },
    "name": "scene_adapter_bezier_drag_unsnapped"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
startYes
view_refYes
budget_msNo
request_idYes
scene_tokenYes
view_fingerprintYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior3/5

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

With no annotations, the description does carry real behavioral weight: it discloses that Snap to Pattern/Smart Guide is turned off for the duration, that paired Release restores original state including on failure, and that no arbitrary QAction/setting/key is touched. It is silent on preconditions (validity or freshness of scene_token/view_fingerprint), failure modes beyond cleanup, and whether the operation is atomic or repeatable.

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 text is short and front-loads the mode, but it is broken into fragments ("No arbitrary QAction/setting/key.") and jargon phrases ("four-phase", "current-owner actions") that consume space without conveying actionable meaning. Length is fine; information density is low.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter, 6-required gesture tool with no annotations, no output schema, and no parameter documentation, the description should at minimum explain the identity tokens and coordinate semantics. It covers none of that, so an agent cannot call it correctly from this definition alone.

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 seven parameters have 0% schema description coverage and the description mentions none of them — not start/end, view_ref, view_fingerprint, scene_token, request_id, or budget_ms. An agent gets no meaning for the required tokens or the coordinates beyond their bare type names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening line, "Fixed four-phase Bezier batch with only Snap to Pattern/Smart Guide temporarily off," restates the tool name in internal jargon rather than saying plainly that it performs a Bezier drag gesture from a start point to an end point. It never states the verb/resource in agent-readable terms, and it does not explicitly distinguish itself from the sibling scene_adapter_bezier_drag beyond the word "unsnapped".

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?

"Triggered only when needed, then restored" describes internal mechanics, not when the agent should select this tool over scene_adapter_bezier_drag. The only usable guidance is the negative caveat "Does not prove semantic hit or mm precision," which hints at a limitation but states no condition for use or exclusion.

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