Skip to main content
Glama
Silhouette Studio MCP Server

Silhouette Studio MCP Server

by WarlemJung

silhouette_clear_shapes

DestructiveIdempotent

Remove all shapes from a design while preserving page dimensions, so you can clear artwork without resetting layout settings.

Instructions

Remove all shapes from a design without resetting page dimensions.

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

Input Schema

NameRequiredDescriptionDefault
designYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful context that page dimensions survive the operation, but says nothing about reversibility, undo, or what happens to shapes referenced elsewhere.

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 with no filler; the destructive scope and the key preservation guarantee both land immediately.

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 simple one-parameter destructive tool, the annotations plus the page-dimension guarantee cover most of what an agent needs. The unexplained "design" argument is the remaining gap, and it is a real one given zero schema coverage.

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?

There is one required parameter ("design") with 0% schema description coverage, and the description never explains whether it is an ID, name, or object. With low coverage the description is expected to compensate, and it does not.

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?

States a specific verb and resource ("Remove all shapes from a design") and adds a scope qualifier ("without resetting page dimensions") that separates it from a full design reset. It does not explicitly name silhouette_remove_shape as the single-shape alternative, so sibling differentiation is implied rather than stated.

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?

The phrase "without resetting page dimensions" hints at when this is preferable to recreating or deleting a design, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative. Usage must be inferred from the scope qualifier.

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