Skip to main content
Glama
ScientiaAI

@textile-designer-ai/mcp

by ScientiaAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Super Scaler

td_super_scaler

Enlarge low-resolution, blurred, or compressed images up to 8x using AI to rebuild lost detail for large-format printing. Saves results and returns file paths.

Instructions

Super Scaler: AI enlargement 2x/4x/8x with detail enhancement. Best for: rescuing low-resolution, blurred, compressed or old images (72 dpi archive JPEGs, small web images) by rebuilding lost detail and enlarging up to 8x for large-format printing. Result files are saved to disk and their paths returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoAI Mode: mode_1 (Neutral, Recommended): Suits most images. mode_2 (Creative): Pushes harder on heavily blurred or degraded sources. 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.
output_sizeNoOutput Size: 2x (2x, Recommended): About twice the input size. 4x (4x): About four times the input size; takes considerably longer. 8x (8x): About eight times the input size; the slowest option. Not available on Truly Unlimited plans. 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.
estimate_onlyNoOnly return the credit estimate; nothing is uploaded or charged.
processing_sizeNoQuality Mode: original_size (Keep original, Recommended): Processes the input at its own size. enlarge_to_1100px (Enlarge to 1100px): Pre-enlarges a small source before upscaling, which helps when the input is very small; it does not change the result size. 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.
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).
detail_enhancementNoDetail Enhancement Options: neutral (Pure Match, Recommended): Keeps detail faithful to the input. more_detailed (Prism Shift): Invents finer texture, at some risk of drifting from the original. 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.

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 already declare the safety profile (not read-only, not idempotent, open world), so the bar is lower. The description adds genuinely useful behavior not covered anywhere else in structured fields: results are written to disk and their paths are returned. It still omits the async/task_id flow (wait=false), credit spend, and job-failure behavior, so it is not fully transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the capability, then the ideal use case, then the output artifact. Every sentence earns its place and nothing is repeated from the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Wait – this is an 11-parameter tool. Reconsidering: for a tool of this complexity the description covers what it does, when to use it, and where results go, and the 100%-covered schema carries all parameter semantics. The only missing piece is the task_id/async lifecycle. Lowering to 4.

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 coverage is 100% and the parameter descriptions are unusually rich (enums explained, recommended values marked, 'never choose for the user' guidance). The description only restates the 2x/4x/8x range and detail enhancement, which the schema already documents, so per the baseline rule a 3 is correct.

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?

Names a specific verb+resource+scope: 'AI enlargement 2x/4x/8x with detail enhancement.' An agent can tell this is an upscaler versus a denoiser/anti-blur tool from the 'rebuilding lost detail and enlarging' framing, but no sibling is named explicitly, so the differentiation is implicit rather than stated.

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 concrete triggering condition (low-resolution, blurred, compressed, or old 72 dpi archive JPEGs and small web images destined for large-format printing). It stops short of stating when NOT to use it or naming the overlapping alternative (td_anti_blur) for blur-only cases.

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