Skip to main content
Glama
Silhouette Studio MCP Server

Silhouette Studio MCP Server

by WarlemJung

silhouette_add_registration_marks

Adds standard Silhouette Print & Cut 3-corner registration marks to a design layer, enabling accurate print-and-cut alignment of printed artwork with cut paths.

Instructions

Add standard Silhouette Print & Cut 3-corner registration marks (top-left square, top-right L-bracket, bottom-left L-bracket) on layer 'REGMARK'.

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

Input Schema

NameRequiredDescriptionDefault
layerNoREGMARK
designYes
inset_mmNo
arm_len_mmNo
arm_thick_mmNo
mark_size_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

The description adds real behavioral detail beyond the annotations by naming the write target layer 'REGMARK' and the exact marks produced. It does not explain the implications of idempotentHint=false — whether re-running appends duplicate marks — nor whether existing marks on that layer are replaced, which matters for a non-idempotent mutating tool.

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 that names the operation, the mark geometry, and the target layer with no filler. 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.

Completeness2/5

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

For a non-idempotent mutation tool with six parameters at 0% schema coverage and no output schema, the description should clarify the geometry parameters and what happens to pre-existing marks on the layer. Instead it covers only the layer and the mark shapes, leaving the caller to guess at units and overwrite semantics.

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%, but the definition does describe the layer parameter's role and its default value, which is the only parameter with semantic nuance in the description. The five numeric geometry parameters (inset, arm length, arm thickness, mark size) are left to the bare schema titles with units only in the property names.

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 (add) and a precisely-scoped resource: Silhouette Print & Cut 3-corner registration marks, with the exact geometry enumerated (top-left square, top-right L-bracket, bottom-left L-bracket) and the target layer named. This clearly separates it from generic siblings like silhouette_add_rectangle or silhouette_add_polygon.

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?

Mentioning 'Print & Cut' implies the workflow context in which this tool is appropriate, which is better than nothing. However, there is no explicit when-to-use statement, no prerequisites (e.g. page/carrier setup), and no guidance on when to use this versus manually composing marks with the primitive shape tools.

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