Skip to main content
Glama
ScientiaAI

@textile-designer-ai/mcp

by ScientiaAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Anti-Blur

td_anti_blur

Sharpen blurred designs and photos by removing blur, noise, and softness. Use Pro mode for most images or Legacy for badly degraded files.

Instructions

Anti-Blur: sharpen a blurred design. Pro mode (recommended) or Legacy mode; files over 20 MB run in Legacy automatically. Best for: removing blur, noise and softness from a design or photo: out-of-focus or motion-blurred images, soft smartphone fabric photos, blurry social-media references. 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: pro (Pro Mode, Recommended): The standard de-blur model; suits most images. legacy (Legacy Mode): A restoration engine for badly degraded images; faster than Pro. Files over 20 MB run in Legacy automatically. 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.
output_dirNoFolder to save results in. Default: the folder of the input image (or the current directory for URL inputs). Files are never overwritten.
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.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, destructiveHint=false. The description usefully adds the automatic 20 MB Legacy fallback and that result files are written to disk with paths returned — real behavior beyond annotations. It still omits cost/credit implications, processing time expectations, and failure modes.

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 purpose, then a compact mode note and a use-case list. Well-structured with no filler, though the use-case enumeration is slightly long relative to the rest.

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-param, no-output-schema tool, the description covers what it does, when it applies, the mode/auto-fallback behavior, and that paths are returned. Credit cost and typical runtime are not addressed but the schema handles most operational detail.

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 parameters are fully documented in the schema (including the mode prompt-behavior rule, wait, estimate_only, output_dir non-overwrite). The description adds only the mode/20 MB note, so baseline 3 is correct.

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?

Specific verb+resource ('sharpen a blurred design') with concrete use cases (out-of-focus, motion-blur, soft fabric photos, blurry social references) that distinguish it from siblings like td_super_scaler or td_fabric_texture_removal. An agent can route to this tool immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'Best for' list gives clear positive fit signals, but there is no explicit when-NOT-to-use guidance or routing versus sibling de-blur/upscale tools. The mode guidance (Pro recommended, auto-switch to Legacy over 20 MB) is helpful context but not alternative-selection 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