Skip to main content
Glama
Silhouette Studio MCP Server

Silhouette Studio MCP Server

by WarlemJung

silhouette_add_star

Add a star shape to a vector cut design by setting point count (3–64), center position, outer and inner radii, and rotation angle.

Instructions

Add a star with the given number of points (3-64). inner_radius_mm must be smaller than outer_radius_mm (about 40% gives a classic star). With rotation_deg=0 one tip points up.

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>",
      "outer_radius_mm": "<outer_radius_mm>",
      "inner_radius_mm": "<inner_radius_mm>"
    },
    "name": "silhouette_add_star"
  }
}

Input Schema

NameRequiredDescriptionDefault
cx_mmYes
cy_mmYes
labelNo
layerNoCUT
designYes
pointsNo
rotation_degNo
inner_radius_mmYes
outer_radius_mmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only declare the operation is a non-read-only, non-destructive, non-idempotent mutation. The description adds real behavioral constraints absent from structured data: the points range 3-64, the invariant that inner_radius_mm must be smaller than outer_radius_mm, and the orientation semantics of rotation_deg=0. It stops short of saying what happens on constraint violation or what identifier comes back.

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?

Two tight sentences, with the core action and its key constraint front-loaded and the optional tuning hints trailing. No filler, no restatement of the tool name, and each clause carries distinct information.

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 9-parameter creation tool with no output schema and sparse annotations, the description covers geometry semantics but omits what 'design' refers to, the coordinate origin for cx_mm/cy_mm, and what the call returns. Adequate to construct a valid call for the radius parameters, but not complete for the full parameter set.

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 description coverage is 0%, so the description must carry parameter meaning. It does well on the non-obvious ones, explaining points range, the inner/outer radius relationship with a 40% heuristic, and rotation orientation. However, cx_mm, cy_mm, design, label, and layer are left entirely unexplained, so half the surface still relies on bare titles.

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 states a specific verb and resource: 'Add a star with the given number of points (3-64).' An agent can immediately tell this creates a star shape rather than a circle, ellipse, or polygon. It doesn't differentiate itself from the closely related silhouette_add_polygon sibling, which a single clause could have fixed.

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: nothing says when to pick a star over silhouette_add_polygon, whether the target design must already exist, or what preconditions apply. The construction hints (40% inner radius, rotation) are shape-building tips rather than usage routing, so an agent must infer the calling context.

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