Skip to main content
Glama
ScientiaAI

@textile-designer-ai/mcp

by ScientiaAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Dress to Design

td_dress_to_design

Extract the print from a garment, mockup, or outfit photo and turn it into a flat, printable 2D design saved to disk.

Instructions

Dress to Design: extract the print from a garment photo as a flat design. Modes: advanced_extraction (recommended), fine_detail, inspired_pattern, all_modes (one output per mode). 1-4 outputs. Best for: getting a flat, printable 2D design from a photo of a garment, mockup or outfit (worn by a person, on a mannequin or flat-lay). Result files are saved to disk and their paths returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNoWait for the job and save the outputs (default true). false returns the task_id right after submit.
imageYesSource image: a local file path or an http(s) URL. PNG, JPEG or WebP, up to 80 MB and 5000 px per side.
model_typeNoExtraction Model: advanced_extraction (Advanced, Recommended), fine_detail (Fine Detail), inspired_pattern (Inspired), all_modes (All Modes). Required: pass the mode the user named. If the user did not name one, omit it and the tool returns the modes to show them; never choose for the user. Call describe_tool for what each option does.
output_dirNoFolder to save results in. Default: the folder of the input image (or the current directory for URL inputs). Files are never overwritten.
num_outputsNoNumber of outputs (1-4, default 1). Number of Outputs. Ignored for all_modes. On a Truly Unlimited plan single modes make one image per run.
estimate_onlyNoOnly return the credit estimate; nothing is uploaded or charged.
review_settingsNoOmit it and the tool first asks whether to use the recommended settings or adjust them (unless the call already sets some). true: ask each setting one by one. false: run with the given or recommended settings without asking; pass it only after the user chose that.
timeout_secondsNoHow long to wait for the job before returning its task_id (default 240).
unlimited_bundleNoRequest the Unlimited bundle for this run (only has effect on Unlimited plans; the server decides).
advanced_remove_workNoRemove work (advanced_extraction only): also strip embroidery, zari, sequins and other surface work, reproducing only the base printed textile. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorld=true), and the description adds genuine operational context beyond them: results are saved to disk with paths returned, files are never overwritten, estimate_only charges nothing, and the Unlimited bundle is server-decided. It doesn't discuss rate limits or failure behavior, so not a 5.

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?

The purpose and mode list are front-loaded in the first two sentences, and the result-file behavior closes it out. It is dense but every clause carries information; no padding or repetition.

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 correctly states what comes back (files on disk with returned paths) and covers mode, count and estimate behavior. Minor gaps remain around failure/timeout behavior for long jobs, but nothing essential to a correct call is missing.

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?

Schema description coverage is 100%, so the schema already documents all ten parameters in detail. The description echoes the mode names and output count but adds only marginal semantics (e.g. 'one output per mode') on top of what the schema states. Baseline 3 is appropriate.

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 resource: 'extract the print from a garment photo as a flat design.' It also enumerates the modes and the 1-4 output count, so an agent can tell it apart from siblings like td_sketch_to_design or td_embroidery_effect without opening the 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 'Best for' clause gives clear context (garment photo, mockup or outfit; worn, mannequin or flat-lay), and the schema's mode field instructs the agent never to choose a mode for the user and to call describe_tool. No explicit when-not or named sibling alternative is given, which keeps it below a 5.

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

Deploy Server

Other Tools