Skip to main content
Glama
Sign In
>sdcraft-mcp

>sdcraft-mcp

by TimkoNZT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

upscale_image

Increase image resolution by applying RGB ESRGAN with a server-configured upscale model.

Instructions

Upscale an image via RGB ESRGAN (requires an upscale model configured on the server).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "image": "<image>"
    },
    "name": "upscale_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYesPath to the image (or base64/dataURL)
repeatsNo
upscalerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It mentions the backend method and a server prerequisite but does not disclose whether the operation is synchronous, what happens if the model is missing, how 'repeats' affects scaling, or what the response contains.

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?

The description is a single front-loaded sentence with no filler. The prerequisite is placed clearly in parentheses and does not obscure the core action.

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

Completeness2/5

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

With no annotations, no output schema, and two of three parameters undocumented, the description leaves significant gaps. An agent cannot tell what the return value is, how repeated upscaling works, or what upscaler names are valid, making it insufficient for a three-parameter image-processing tool.

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

Parameters2/5

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

Schema description coverage is only 33%: the 'image' parameter is described, but 'repeats' and 'upscaler' have no schema descriptions. The tool description does not explain what 'repeats' means, what values 'upscaler' accepts, or how the model configuration relates to the 'upscaler' parameter.

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?

The description names a specific verb and resource ('Upscale an image') plus the underlying method (RGB ESRGAN). It is clear what the tool does, although it does not explicitly contrast with siblings like edit_image or generate_image.

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 parenthetical states a prerequisite (an upscale model must be configured on the server), which is useful context. However, there is no explicit guidance on when to choose this tool over edit_image or generate_image, nor any exclusion conditions.

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