Skip to main content
Glama

Creative Upscale

creative_upscale

Upscale artistic images with creative enhancement that adds detail and improves quality beyond simple scaling. Supports images up to 5MB and 16 megapixels.

Instructions

Upscale an image with creative enhancement — adds detail and improves quality beyond simple scaling. Best for artistic images where added creative detail is desirable. Input image must be max 5MB and <16MP.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageYesImage to upscale as a URL or base64-encoded string. Max 5MB, <16MP.
image_formatNoOutput format.
Behavior3/5

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

Annotations are minimal (readOnlyHint=false, openWorldHint=true). The description discloses input constraints (max 5MB, <16MP) and that the tool adds detail and improves quality. However, it does not describe behavioral traits like irreversibility, cost, or effect on original image. Adequate but not thorough.

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?

Two sentences, front-loaded with main action, then usage guidance and constraint. No filler words; every sentence adds value. Extremely concise.

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 simple tool with 2 parameters and no output schema, the description covers core behavior, input constraints, and usage context. It could mention output format possibilities, but the schema covers that. Contextually sufficient.

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%, so the schema already documents both parameters. The description repeats the input constraint from the schema but adds no significant new meaning about parameters, such as defaults or behavior of image_format.

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?

The description clearly states the tool's purpose: 'Upscale an image with creative enhancement.' It distinguishes from simple scaling and implies differentiation from sibling 'crisp_upscale' by specifying 'added creative detail.' The verb and resource are specific.

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 description provides guidance on when to use: 'Best for artistic images where added creative detail is desirable.' It implies when not to use (non-artistic images) but does not explicitly name alternatives. This is clear but lacks explicit exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BartWaardenburg/recraft-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server