Skip to main content
Glama
Silhouette Studio MCP Server

Silhouette Studio MCP Server

by WarlemJung

silhouette_nest_shapes

Packs 2D shapes into rectangular sheet layouts with zero overlap and defined spacing, skipping REGMARK registration marks; use dry_run to preview placement without moving shapes.

Instructions

Optimise 2D rectangular sheet nesting (MaxRects Best Short Side Fit) to pack shapes inside the usable cutting area with zero overlap and guaranteed spacing_mm clearance. Automatically skips and avoids any REGMARK registration marks on the page. Set dry_run=true to compute placement metrics without modifying shape coordinates.

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_nest_shapes"
  }
}

Input Schema

NameRequiredDescriptionDefault
designYes
dry_runNo
margin_mmNo
shape_idsNo
spacing_mmNo
allow_rotationNo
rotation_step_degNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Adds real value beyond annotations by disclosing that coordinates are modified, that spacing_mm clearance is guaranteed, and that REGMARK shapes are skipped — consistent with readOnlyHint=false. Still silent on failure behavior (what happens to shapes that cannot fit), whether existing relative layout is lost, and idempotency, which matters given idempotentHint=false.

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 tight sentences, front-loaded with the core operation, then a behavioural guarantee, then the dry_run escape hatch. Very little waste, though the algorithm-name parenthetical is more implementation detail than selection aid.

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?

A mutating, seven-parameter tool with no output schema and zero schema coverage needs substantially more parameter explanation than is present. The behavioural picture (what changes, what is preserved) is good, but the calling surface for the other five arguments is left entirely to inference.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 7 parameters, so the description must carry the load, but it only explains spacing_mm and dry_run. Five parameters are undocumented anywhere — notably margin_mm (default -1 is unintuitive), shape_ids, allow_rotation, and rotation_step_deg.

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?

Names a specific verb and resource: optimise 2D rectangular sheet nesting of shapes, and even names the algorithm (MaxRects Best Short Side Fit). It is clearly distinct from the add_/transform_/delete_ siblings, though it never explicitly contrasts itself with any of them.

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?

Gives a concrete conditional for dry_run=true ('compute placement metrics without modifying coordinates'), which is genuine usage guidance. However it says nothing about when nesting is appropriate versus, say, grid_duplicates or manual transform, and states no prerequisites such as requiring existing shapes in the design.

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