Skip to main content
Glama
ScientiaAI

@textile-designer-ai/mcp

by ScientiaAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Colourways

td_colourways

Generate 6–48 alternate colourways for a textile print, keep up to 8 source colours, and save options to disk to build pastel, deep, or dark ranges from one design.

Instructions

Colourways: generate colourway options for the design (6, 12, 24 or 48), optionally keeping up to 8 of its colours. grid true also makes a buyer sheet. Best for: a buyer wants the same print in other colours, or a range needs pastel, deep and dark stories from one bestseller. Result files are saved to disk and their paths returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dpiNoOutput resolution in ppi (72-500). Omit to keep the image's own resolution.
gridNoAlso make a buyer sheet (every option on one page). Default true.
waitNoWait for the job and save the outputs (default true). false returns the task_id right after submit.
countNoOptions to make: 6, 12 (default), 24 or 48 (1-50 accepted). Large designs allow at most floor(600 / megapixels); more drops to the largest that fits.
imageYesSource image: a local file path or an http(s) URL. PNG, JPEG or WebP, up to 80 MB and 5000 px per side.
promptNoBrief for the colourist (max 4000 characters), e.g. 'SS27 Europe high street', 'AW26 menswear', 'Kids' nursery', 'Bridal and occasion', 'Middle-East luxury', 'Scandinavian minimal'.
harmonyNoColour story: contrast (Bold contrast, Recommended): Motif and ground far apart. family (Close family): Everything within one arc of the wheel. mono (One colour, many shades): One hue, separated by light and dark. 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.
output_dirNoFolder to save results in. Default: the folder of the input image (or the current directory for URL inputs). Files are never overwritten.
tone_rangeNoMood: all (Surprise me, Recommended): Any tonal range. pastel (Fresh pastels): Light pastel tones. mid (Everyday mid tones): Mid tones. deep (Rich and deep): Deep, saturated tones. vivid (Bright and bold): Bright, vivid tones. dark (Dark grounds): Dark grounds. neutral (Quiet neutrals): Muted neutral tones. 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.
fine_detailNoDelicate print: thin lines or pale motifs on a light ground. Default false.
estimate_onlyNoOnly return the credit estimate; nothing is uploaded or charged.
locked_colorsNoKeep these colours: up to 8 hex colours from the design (e.g. the ground or a brand colour), snapped to the design's nearest dominant colour. td_color_matching_extract_colors lists the design's colours.
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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (write, open-world, non-idempotent, non-destructive). The description adds genuinely useful behavior not in the annotations: results are written to disk and file paths are returned, and grid=true also produces a buyer sheet. It omits the async/job and credit-cost aspects, but the incremental disclosure over annotations is real.

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 core action, then eligibility, then output behavior. Every sentence earns its place, though the 'Best for' sentence packs several scenarios and runs a little long.

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?

For a 15-parameter generative tool with no output schema, the description usefully closes the return-value gap by stating files are saved to disk and paths returned. It leaves async/job and cost behavior to the schema, but the coverage is otherwise solid for an agent to call it correctly.

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 15 parameters in detail (enums, ranges, defaults). The description only restates a few of these (counts, locked colours, grid buyer sheet), adding no syntax or format meaning beyond the schema, so the baseline of 3 applies.

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 ('generate colourway options for the design') plus the concrete option counts (6/12/24/48) and the locked-colour behavior. This is clear and non-tautological, but it does not explicitly differentiate itself from the many sibling colour tools (e.g. td_color_matching_regenerate) that an agent might confuse it with.

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' sentence gives concrete usage scenarios: a buyer wanting the same print in other colours, or a range needing pastel/deep/dark stories from one bestseller. That is strong when-to-use guidance, though it offers no explicit when-not or named alternatives.

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