Skip to main content
Glama
recraft-ai

Recraft AI MCP Server

Official

crisp_upscale

Enhance image clarity and sharpness with Recraft AI MCP Server's upscale tool. Input a local file or URL to receive a higher-quality, upscaled image and preview.

Instructions

Crisp upscale of the input image using Recraft. This operation takes an input image and returns an upscaled image, making the image sharper and cleaner. This version of upscale is much cheaper and faster than creative upscale. Local path or URL to resulting image and its preview will be returned in the response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageURIYesImage to use as an input. This can be a URL (starting with http:// or https://) or an absolute file path (starting with file://).

Implementation Reference

  • The main handler function for the crisp_upscale tool. Downloads the input image, calls the Recraft API's crispUpscale method, and returns the result formatted for MCP.
    export const crispUpscaleHandler = async (server: RecraftServer, args: Record<string, unknown>): Promise<CallToolResult> => {
      try {
        const { imageURI } = z.object({
          imageURI: z.string(),
        }).parse(args)
    
        const imageData = await downloadImage(imageURI)
    
        const result = await server.api.imageApi.crispUpscale({
          image: await imageDataToBlob(imageData),
          responseFormat: 'url',
          expire: server.isLocalResultsStorage,
        })
    
        return await server.transformSingleImageOperationToCallToolResult(result.image, 'Crisp upscale completed.')
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Crisp upscale error: ${error}`
            }
          ],
          isError: true
        }
      }
    }
  • Tool definition including name, description, and input schema for validation.
    export const crispUpscaleTool = {
      name: "crisp_upscale",
      description: "Crisp upscale of the input image using Recraft.\n" +
        "This operation takes an input image and returns an upscaled image, making the image sharper and cleaner.\n" +
        "This version of upscale is much cheaper and faster than creative upscale.\n" +
        "Local path or URL to resulting image and its preview will be returned in the response.",
      inputSchema: {
        type: "object",
        properties: {
          imageURI: PARAMETERS.imageURI,
        },
        required: ["imageURI"]
      }
    }
  • src/index.ts:68-82 (registration)
    Registration of crispUpscaleTool in the MCP server's list of available tools.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          generateImageTool,
          createStyleTool,
          vectorizeImageTool,
          imageToImageTool,
          removeBackgroundTool,
          replaceBackgroundTool,
          crispUpscaleTool,
          creativeUpscaleTool,
          getUserTool,
        ],
      }
    })
  • src/index.ts:114-115 (registration)
    Dispatch to crispUpscaleHandler in the MCP call tool request handler switch statement.
    case crispUpscaleTool.name:
      return await crispUpscaleHandler(recraftServer, args ?? {})
  • TypeScript interface defining the request schema for the underlying Recraft API crispUpscale endpoint.
    export interface CrispUpscaleRequest {
        image: Blob;
        expire?: boolean;
        imageFormat?: ImageFormat;
        responseFormat?: ResponseFormat;
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the operation (upscaling), cost/performance characteristics (cheaper and faster), and output format (local path or URL with preview). However, it lacks details about rate limits, authentication needs, file size limits, or error conditions that would be valuable for an agent.

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?

The description is appropriately sized with four sentences that each add value: purpose statement, outcome explanation, comparison to alternatives, and output format. It's front-loaded with the core functionality. Minor deduction for slightly repetitive phrasing about the image input/return.

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 single-parameter tool with no annotations and no output schema, the description provides good coverage: purpose, differentiation from alternatives, behavioral context (cheaper/faster), and output format. It could be more complete by mentioning potential limitations or error cases, but it's substantially adequate for the tool's complexity.

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?

The schema description coverage is 100%, so the schema already fully documents the single parameter. The description doesn't add any parameter-specific information beyond what's in the schema, maintaining the baseline score of 3 when schema coverage is complete.

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 specific action ('crisp upscale'), resource ('input image'), and technology ('using Recraft'), distinguishing it from sibling tools like creative_upscale. It explicitly mentions the outcome ('making the image sharper and cleaner'), providing a complete purpose statement.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool versus alternatives: 'This version of upscale is much cheaper and faster than creative upscale.' This directly compares it to the sibling tool creative_upscale, giving clear context for selection.

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

Related 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/recraft-ai/mcp-recraft-server'

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