Skip to main content
Glama
ScientiaAI

@textile-designer-ai/mcp

by ScientiaAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

3D Effect

td_3d_effect

Add 3D depth and embossing to flat textile designs, turning 2D patterns into relief visuals with shadows for buyer previews. Saves result files and returns their paths.

Instructions

3D Effect: add depth/relief to the design. similar (1-4 outputs) or same (keeps the design fixed, one output). Best for: turning a flat 2D textile design into a 3D look with depth, shadows and embossing, e.g. showing a buyer embossed printing without a physical sample. Clear, well-defined patterns work best. 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.
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.
depth_levelNoDepth Level: low (Subtle Depth): Light embossing with minimal shadows. medium (Moderate Depth, Recommended): Balanced 3D effect with noticeable layers. high (Dramatic Depth): Strong 3D effect with pronounced shadows. 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.
num_outputsNoNumber of outputs (1-4, default 1). Number of Outputs; only for similar. 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.
similarity_modeNoSimilarity Mode: similar (Similar Image, Recommended): Enhance while keeping the essence recognizable; may vary the motifs; 1-4 outputs. same (Same Image): Preserve the exact design, only add 3D effects; one output. 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.
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.6/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly=false, destructive=false, openWorld=true, idempotent=false). The description adds one genuinely useful non-annotation fact – results are written to disk and paths returned – plus a pattern-quality caveat, but says nothing about credit cost, processing time, or how the source image is treated.

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 purpose, then use case, then a useful output note. Four compact sentences with little waste, though the mode parenthetical slightly duplicates the schema.

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 an 11-parameter tool with no output schema, the description covers purpose, best-fit input, mode trade-offs, and the return shape (file paths). The complex interaction flags (review_settings, wait, estimate_only) are well documented in the schema, so the remaining gap is minor.

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 fully documents all 11 parameters, including the mode enums and interaction flags. The description only echoes the similar/same modes and the 1-4 output count, adding no syntax or behavioral detail beyond the schema; baseline 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 concrete verb+resource: 'add depth/relief to the design', plus the 2D-flat-to-3D framing and the embossing use case. This clearly separates it from siblings like td_embroidery_effect or td_sketch_to_design, though it never names an alternative explicitly.

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 (flat 2D textile design, buyer presentations) and 'Clear, well-defined patterns work best' sets an input-suitability expectation. It also sketches the similar-vs-same choice, but offers no when-not-to-use guidance 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