Skip to main content
Glama
Silhouette Studio MCP Server

Silhouette Studio MCP Server

by WarlemJung

silhouette_import_svg

Imports SVG artwork into a design by converting curves to millimeter outlines for DXF export, enabling Silhouette Studio Standard Edition to use SVG files it cannot open natively.

Instructions

Read an SVG file from disk, convert outlines (curves flattened to mm segments) and add them to the design for DXF export. This bridges SVG artwork into Silhouette Studio Standard Edition (which cannot open SVG natively). target_width_mm / target_height_mm > 0 scale artwork (uniformly if only one is given); artwork's top-left corner is placed at (x_mm, y_mm). Text and embedded images are skipped (convert text to outlines or use silhouette_add_text).

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>",
      "svg_path": "<svg_path>"
    },
    "name": "silhouette_import_svg"
  }
}

Input Schema

NameRequiredDescriptionDefault
x_mmNo
y_mmNo
layerNoCUT
designYes
svg_pathYes
rotation_degNo
target_width_mmNo
target_height_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare the non-read-only, non-destructive, non-idempotent profile, so the bar is lower; the description still adds real substance by disclosing that curves are flattened into mm segments (a lossy conversion) and that text and embedded images are silently skipped. It does not say whether skipped elements are reported back, whether a missing or malformed file raises an error, or whether repeated imports duplicate shapes.

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?

Roughly four sentences with the core action front-loaded and the parameter semantics grouped after it; nothing is padded or repeated. The parenthetical about Studio Standard Edition is slightly parenthetical-heavy but earns its place by explaining why the tool exists.

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

Completeness4/5

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

For an eight-parameter mutating import tool with no output schema, the description supplies the placement, scaling, and lossy-conversion semantics an agent needs before calling it, plus the text fallback. The remaining gap is return behavior — whether the imported shape handles or a list of skipped elements comes back — which matters for chaining follow-up transforms.

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 carries the load and does explain the non-obvious parameters: target_width_mm/target_height_mm scaling with uniform behavior when only one is given, and that (x_mm, y_mm) anchors the artwork's top-left corner rather than its center. Layer, rotation_deg, design, and svg_path get no treatment, so half of the eight parameters remain documented only by their names and defaults.

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

Purpose5/5

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

The description opens with a specific verb chain — read an SVG, flatten curves to mm segments, add outlines to a design for DXF export — and identifies the resource precisely. It explicitly contrasts itself with silhouette_add_text for text handling, so an agent can separate it from the text/primitive siblings without opening a schema.

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

Usage Guidelines4/5

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

It explains the scenario that selects this tool (bringing SVG artwork into Studio Standard Edition, which cannot open SVG natively) and points to the alternative for text via silhouette_add_text. It stops short of stating exclusions such as file-size limits, supported SVG feature sets, or when to prefer native shape primitives instead, but the primary routing context is clear.

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