Skip to main content
Glama
ScientiaAI

@textile-designer-ai/mcp

by ScientiaAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Fabric Texture Removal

td_fabric_texture_removal

Remove fabric weave and surface texture from photos of printed fabric while keeping artwork and colours, turning scans or swatches into clean digital designs.

Instructions

Fabric Texture Removal: flatten the fabric weave/texture out of a photographed design. 1-4 outputs. Best for: turning a flat scan or photo of printed fabric into a clean digital design: removes the weave and surface texture while keeping the artwork and its colours, e.g. digitising an old swatch. 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.
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). On a Truly Unlimited plan every run makes one 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

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). The description adds behavioral value beyond that: it states 1-4 outputs are produced and that result files are written to disk with paths returned, so an agent knows outputs are persisted rather than inlined. It stops short of cost/auth/overwrite details.

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?

Front-loaded with the core action, then the best-for context, then the output behavior. All sentences earn their place, though the best-for clause and the 1-4 outputs detail make it slightly run-on rather than maximally tight.

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 carries the burden of describing returns and does so ('files saved to disk, paths returned') and notes output count. For an 8-param tool with full schema coverage and annotations, this is nearly complete, missing only cost/overwrite specifics that live in the schema.

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 all eight parameters are fully documented in the schema itself (including output_dir non-overwrite, wait, num_outputs limits). The description adds no parameter-level syntax or semantics beyond what the schema provides, so the baseline of 3 applies.

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 (flatten/remove) and resource (fabric weave/texture from a photographed design), with a concrete example (digitising an old swatch). This is clearly distinguishable from siblings like td_anti_blur or td_background_removal, which target different artifacts.

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 a clear context for use (flat scan/photo of printed fabric -> clean digital design) with an example. It does not, however, name when NOT to use it or point to alternative tools for adjacent tasks.

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