Skip to main content
Glama
Silhouette Studio MCP Server

Silhouette Studio MCP Server

by WarlemJung

silhouette_add_ellipse

Adds a rotated ellipse to a Silhouette design at specified center coordinates and horizontal/vertical radii for precise vector cut layout creation.

Instructions

Add an ellipse centred at (cx_mm, cy_mm) with radii rx_mm (horizontal) and ry_mm (vertical), rotated clockwise by rotation_deg.

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": {
      "design": "<design>",
      "cx_mm": "<cx_mm>",
      "cy_mm": "<cy_mm>",
      "rx_mm": "<rx_mm>",
      "ry_mm": "<ry_mm>"
    },
    "name": "silhouette_add_ellipse"
  }
}

Input Schema

NameRequiredDescriptionDefault
cx_mmYes
cy_mmYes
labelNo
layerNoCUT
rx_mmYes
ry_mmYes
designYes
rotation_degNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare a non-readonly, non-destructive, non-idempotent mutation, so the safety profile is covered. The description adds two genuinely useful beyond-schema facts: units are millimetres and rotation is clockwise. It does not disclose what is returned, whether the shape is added to a specific design or current page, or what happens on failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, and the coordinate/radius definitions arrive before the rotation detail. Every clause carries information an agent needs.

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?

For a document-mutating add operation with eight parameters and no output schema, the definition covers geometry well but omits the design-targeting semantics, the meaning of layer and label, and any indication of what the call returns or how errors surface.

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

Parameters3/5

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

Schema coverage is 0%, so the description must carry the load, and it does explain five of eight parameters well - rx_mm is horizontal, ry_mm is vertical, and rotation_deg is clockwise, which resolves a real ambiguity. However 'design', 'layer' (default 'CUT'), and 'label' are never described, leaving half the non-geometry surface undocumented.

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?

The description uses a specific verb and resource ('Add an ellipse') and defines the geometry precisely through its centre coordinates and two radii. It is clear enough to distinguish it from add_rectangle or add_polygon, though it never explicitly contrasts with add_circle, which is a very close sibling.

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 statement of when to use this tool versus alternatives such as silhouette_add_circle, and no prerequisites stated (for example, whether 'design' must already exist, or whether the shape lands on the current page). Usage must be inferred entirely from the name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.