Skip to main content
Glama
Silhouette Studio MCP Server

Silhouette Studio MCP Server

by WarlemJung

silhouette_make_calibration_file

Idempotent

Creates and exports a calibration DXF with a 100 mm square, circle, rounded rectangle, and perforated score line to verify import scale and set Studio DXF imports to as-is.

Instructions

Create and export a calibration DXF: a 100 x 100 mm square with a 50 mm circle, a 40 x 20 mm rounded rectangle, and a 100 mm perforated score line. Open it in Studio and measure it: if the square is not 100 mm (3.937 in), set Studio Preferences > Import Options > DXF to 'As-is'.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "silhouette_make_calibration_file"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value beyond that: the exact contents of the generated file and the workflow for validating it. It omits where the file is written, whether it overwrites an existing file, and what path 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?

Three sentences, front-loaded with the action, and the geometry enumeration earns its place because those dimensions are what the user measures against. Slightly dense but no filler or restated title.

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 zero-param file-producing tool with no output schema, the description should say where the file lands and what is returned. It covers what is produced and how to verify it, but leaves the agent without a path or filename to act on — a meaningful gap given nothing else documents the return value.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly implies nothing is configurable — the geometry is fixed — which is the right semantic signal for a parameterless calibration fixture.

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 artifact: 'Create and export a calibration DXF', then enumerates the exact geometry (100x100 mm square, 50 mm circle, 40x20 mm rounded rectangle, 100 mm perforated score line). An agent can tell this apart from silhouette_export or silhouette_add_rectangle without opening any 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?

The purpose is clear from context — verifying DXF import scale in Studio — and it gives explicit remediation steps ('set Studio Preferences > Import Options > DXF to As-is') if the measurement is wrong. It does not name alternatives or state when to prefer this over another tool, but for a diagnostic utility that gap is minor.

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