Skip to main content
Glama
ScientiaAI

@textile-designer-ai/mcp

by ScientiaAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Style Transfer

td_style_transfer

Restyle a finished design with a named library style or the look of a second image while preserving its layout. Results are saved to disk and file paths are returned.

Instructions

Style Transfer: restyle the design with a library style or with the style of a second image (image_to_image). Best for: giving a finished design a new artistic surface look (e.g. Watercolor, Oil Painting) or the look of a second image, while the design layout stays intact. 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.
modeNoMode: style_library (Image Style Transfer, Recommended): Restyle the source design with a named library style (style). image_to_image (Image to Image Style Transfer): Apply the look of a second image (the style image) onto the source design, keeping the source layout. 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.
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.
styleNoStyle: watercolor (Watercolor), pastel_drawing (Pastel Drawing), oil_painting (Oil Painting), pencil_sketch (Pencil Sketch), paper_collage (Paper Collage), street_art (Street Art), japanese_ukiyoe (Japanese Ukiyo-e), baroque (Baroque), coloring_book (Coloring Book), art_nouveau (Art Nouveau), vintage_boho (Vintage Boho), floral (Floral), tile_art (Tile Art), surreal (Surreal), expressionist (Expressionist), mosaic (Mosaic), minimal_line_art (Minimal Line Art), stained_glass (Stained Glass), tropical (Tropical), neon (Neon), metallic (Metallic), low_poly (Low Poly), water_action (Water Action). 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. Required in style_library mode; there is no default style. 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.
style_imageNoimage_to_image: path or URL of the website's Source Image (the style donor) whose look is copied onto the design; the design (image) is the website's Target Image.
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).

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?

With annotations already declaring readOnlyHint=false, destructiveHint=false and non-idempotency, the description adds real value by disclosing the output behavior: result files are saved to disk and their paths returned. It also confirms the layout-preserving semantics, though it says nothing about credit costs or the review/estimate flow.

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 purpose, then usage context, then output—no filler. Minor redundancy in restating the tool name, but nothing wasteful.

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 complex 11-parameter, no-output-schema tool, the description covers the two operating modes, the intended use case, and the return format (file paths on disk), which is the key missing piece without an output schema. Credit/bundle/estimate mechanics are left to the schema but are not essential to correct invocation.

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 11 parameters in detail; the description adds essentially no parameter-level meaning beyond reusing the mode/style example names already in the schema. Baseline 3 is appropriate when the schema carries the burden.

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?

The description states a specific verb (restyle) and resource (the design) and explicitly names its two modes (library style vs. image_to_image). It is clear about what it does, though it never distinguishes itself from the nearby sibling td_color_transfer, which an agent could easily 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' clause gives clear usage context: applying an artistic surface look while keeping the design layout intact, including example styles. It lacks explicit when-not-to-use guidance or named alternatives (e.g. color transfer), so it stops just short of full routing guidance.

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