Skip to main content
Glama
ScientiaAI

@textile-designer-ai/mcp

by ScientiaAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Spec Board

td_spec_board

Build a tech-pack style specification board from a garment photo, with optional reference mode to mirror an existing board's layout and sections.

Instructions

Spec Board: build a tech-pack style spec board from a garment photo. Give garment_type, or use Reference mode: a reference_image (an existing spec board) whose layout and sections are mimicked. Best for: turning a garment photo (saree, kurti, suit, lehenga, frock or gown) into a professional specification board for production. 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.
garment_typeNoGarment type: saree (Saree), kurti (Kurti), suit (Suit), lehenga (Lehenga), frock (Frock), gown (Gown), dupatta (Dupatta), all_over (All-over), shirt_tshirt (Shirt/T-shirt), western (Western). 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 unless reference_image is given; there is no default garment. Call describe_tool for what each option does.
estimate_onlyNoOnly return the credit estimate; nothing is uploaded or charged.
reference_imageNoReference mode: a reference spec board (path or URL). When given, the output mimics its sections, layout and styling and garment_type is not used.
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.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and idempotentHint=false, so the write/open-world nature is covered. The description adds output behavior the annotations don't convey: result files are saved to disk and their paths returned, plus the reference-mode mimicry semantics. It stops short of covering cost/auth beyond what the schema (estimate_only) implies.

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 verb+resource, then modes, then 'best for', then output. Four sentences with no filler. Slightly dense with the mode and output details, but each earns its place.

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 9-parameter, enum-bearing tool with no output schema, the description covers the two modes and the disk-output return format, which is the main thing an agent needs that isn't in structured data. Marginal gaps (pricing/auth beyond estimate_only) are minor given the rich schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds genuinely non-schema semantics: the mutual exclusivity of garment_type and reference_image and the fact that reference mode overrides garment_type. That elevates it above the schema-only baseline.

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: 'build a tech-pack style spec board from a garment photo'. It also delineates the two operating modes (garment_type vs reference_image), which is the key distinction an agent must grasp to call it correctly. The purpose is unmistakable.

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 and the mode-selection sentence ('Give garment_type, or use Reference mode') give clear context for when to use each path. It does not, however, name any sibling tool as an alternative for a garment photo that isn't a spec board, so routing among the many td_* tools is left to inference.

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