Skip to main content
Glama
Silhouette Studio MCP Server

Silhouette Studio MCP Server

by WarlemJung

silhouette_describe_design

Read-onlyIdempotent

Summarise a vector cut design: page size, every shape with its bounding box, overall bounds, and warnings for shapes outside the page, inside the safety margin, or with tiny details.

Instructions

Summarise a design: page size, every shape with its bounding box, overall bounds and any warnings (outside the page, inside the safety margin, tiny details).

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

Input Schema

NameRequiredDescriptionDefault
designYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine value beyond that by disclosing the exact content of the response, including the three warning categories, which tells the agent this is a diagnostic read rather than a raw data dump.

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?

One dense sentence, front-loaded with the verb and resource, then the enumerated outputs. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

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

With no output schema, the description must carry the return-value burden, and it does so by listing page size, shape bounding boxes, overall bounds, and warnings. The remaining gap is the ambiguous design parameter, which is left unexplained.

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

Parameters3/5

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

Only one parameter (design) with 0% schema description coverage, and the description does not clarify whether it is a design ID, name, or serialized object. It adds no meaning beyond the bare schema, though the single-parameter surface limits the damage.

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 (summarise) and resource (a design) and enumerates exactly what the summary contains: page size, per-shape bounding boxes, overall bounds, and warnings. It is clearly distinguishable from the add_*/transform_* siblings, though it does not explicitly contrast with silhouette_get_design or silhouette_render_preview.

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?

Usage is only implied: the mention of warnings (outside the page, inside the safety margin, tiny details) suggests this is a validation/inspection step, but the description never says when to prefer it over get_design or render_preview, nor any preconditions.

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