Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

curve_handles

Reads cubic Bezier curves and handle references from a pattern UUID in 2D mm, returning owner and fresh topology/geometry fingerprints; re-read after scene changes.

Instructions

Read cubic Bezier curves and handle refs from the current pattern UUID; XY is 2D mm.

References include their owner and fresh topology/geometry fingerprints. Re-read after any scene change. Unsupported spline encodings are reported without conversion.

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": {
      "pattern_uuid": "<pattern_uuid>"
    },
    "name": "curve_handles"
  }
}

Input Schema

NameRequiredDescriptionDefault
scene_tokenNo
pattern_uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose meaningful traits: XY units in mm, fingerprints being 'fresh', staleness after scene changes, and that unsupported spline encodings are surfaced rather than converted. It says nothing about permissions, error/failure modes, or result shape beyond the bag of fields mentioned.

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?

Three short sentences, front-loaded with the core action and resource, then unit and freshness caveats. No filler, though the fragmented sentence structure is slightly choppy.

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

Completeness3/5

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

No output schema exists, and the description only partially describes returns (owner plus topology/geometry fingerprints) without clarifying the handle record structure. Combined with an entirely undocumented scene_token, a moderately complex read tool is left with clear informational gaps.

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%, so the description must compensate and only partly does: 'from the current pattern UUID' maps loosely to pattern_uuid but adds no format or validation detail. The nullable scene_token parameter is never mentioned or explained, leaving half the inputs undocumented in both schema and prose.

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 (Read) and specific resources (cubic Bezier curves and handle refs) scoped to a pattern UUID. The read framing implicitly contrasts with the sibling set_curve_handle_xy, but no sibling is named, so an agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a useful freshness rule ('Re-read after any scene change'), which tells the agent when to call again. It gives no guidance on when to prefer this over related tools like curve_runtime_capabilities or when handle data is unavailable, so usage is only implied.

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