Skip to main content
Glama
Silhouette Studio MCP Server

Silhouette Studio MCP Server

by WarlemJung

silhouette_add_line

Adds a straight line between two millimeter coordinates, with optional dashed perforated segments for folding cardstock and selectable cut, score, or perf layers.

Instructions

Add a straight line between (x1_mm, y1_mm) and (x2_mm, y2_mm). If dashed=true, creates perforated segments ideal for folding cardstock/papercraft. dash_len_mm: cut segment length (default 3mm); gap_len_mm: un-cut gap length (default 2mm). layer: 'CUT', 'SCORE', 'PERF', etc.

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>",
      "x1_mm": "<x1_mm>",
      "y1_mm": "<y1_mm>",
      "x2_mm": "<x2_mm>",
      "y2_mm": "<y2_mm>"
    },
    "name": "silhouette_add_line"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNo
layerNoCUT
x1_mmYes
x2_mmYes
y1_mmYes
y2_mmYes
dashedNo
designYes
gap_len_mmNo
dash_len_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds real behavior beyond that: what dashed actually produces (perforated segments), the default dash and gap lengths, and valid layer values. It omits consequences the agent would want, such as whether repeated calls create duplicate overlapping shapes (consistent with idempotentHint=false) and what identifier is returned.

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?

Four short sentences, front-loaded with the core operation and coordinates, then the optional dashed behavior, then parameter defaults. Nothing is padded, though the parameter notes read as a terse fragment list rather than fully structured guidance.

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 10-parameter mutating tool with no output schema and no parameter descriptions in the schema, the definition covers the geometry and dash semantics well. It is not complete enough on the two remaining gaps — how to reference the target 'design' and what gets returned (shape ID, index) — for an agent to chain this call confidently.

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% across 10 parameters, so the description must carry the load. It meaningfully documents 8 of them (the four coordinates, dashed, dash_len_mm, gap_len_mm, layer with example values), but leaves 'design' (a required parameter with no indication of whether it is an ID or a name) and 'label' entirely undefined, and the layer enumeration trails off into 'etc.'

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 gives a specific verb ('Add') and resource ('a straight line') plus the exact coordinate inputs that define it, so the agent knows precisely what shape gets created. It does not, however, contrast itself with the sibling 'silhouette_add_polyline', which is the obvious alternative for multi-segment paths.

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?

Usage context is implied rather than stated: the 'dashed=true ... ideal for folding cardstock/papercraft' sentence tells the agent when perforation is appropriate, which is a genuine usage hint. There is no explicit when-not guidance and no pointer to the polyline/rectangle siblings for multi-segment or closed shapes.

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