Skip to main content
Glama
Silhouette Studio MCP Server

Silhouette Studio MCP Server

by WarlemJung

silhouette_new_design

DestructiveIdempotent

Create an empty design canvas using a preset or custom width and height in millimetres, so you can start placing cut shapes. Fails if the design exists unless overwrite is set.

Instructions

Create an empty design (the working canvas). Use a preset (see silhouette_list_page_presets) or give custom width_mm AND height_mm (they override the preset). cut_margin_mm is a safety margin used only for warnings. Fails if the design exists unless overwrite=true.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
presetNomat-12x12
width_mmNo
height_mmNo
overwriteNo
cut_margin_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so safety is largely covered; the description still adds real value by naming the failure mode ('Fails if the design exists unless overwrite=true') and by scoping cut_margin_mm to warnings only. It stops short of describing what is returned or what overwrite destroys.

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 purpose, then the preset/override rule, then the margin caveat, then the failure condition. No filler; the only slack is the parenthetical gloss, which still earns its place.

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?

With six parameters at 0% schema description coverage and no output schema, the description covers most input meaning but says nothing about the return value—likely a design identifier that every silhouette_add_* and export sibling requires. That omission is the main completeness gap for a creation tool.

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

Parameters4/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 the burden, and it explains the two-parameter override relationship, the warning-only role of cut_margin_mm, and the overwrite flag. Only 'name' (self-evident and required) and the actual defaults go unaddressed.

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?

States a specific verb and resource ('Create an empty design') and adds the clarifying gloss '(the working canvas)', which separates it from the add_*_shape siblings that populate an existing design. An agent can tell this is the initial-container tool without inspecting the 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?

Gives explicit selection logic: use a preset (pointing at silhouette_list_page_presets) or supply custom width_mm AND height_mm, which override the preset. It also states the overwrite precondition for the already-exists case. It does not explicitly say when to prefer deletion (silhouette_delete_design) over overwrite, which keeps it short of a 5.

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