Skip to main content
Glama
Ichigo3766

Image Generation MCP Server

by Ichigo3766

get_sd_upscalers

Retrieve a list of available upscaler models for enhancing image resolution and quality, integrated with Stable Diffusion WebUI for efficient image generation workflows.

Instructions

Get list of available upscaler models

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'get_sd_upscalers' tool. It makes a GET request to the Stable Diffusion WebUI API endpoint '/sdapi/v1/upscalers' to retrieve the list of available upscalers, casts the response to UpscalerInfo[], extracts their names, and returns them as a JSON string in the tool response.
    case 'get_sd_upscalers': {
      const response = await this.axiosInstance.get('/sdapi/v1/upscalers');
      const upscalers = response.data as UpscalerInfo[];
      return { content: [{ type: 'text', text: JSON.stringify(upscalers.map(u => u.name)) }] };
    }
  • TypeScript interface defining the structure of upscaler information returned by the Stable Diffusion API, used for typing the response data in the handler.
    interface UpscalerInfo {
      name: string;
      model_name: string;
      model_path: string;
      model_url: string;
      scale: number;
    }
  • src/index.ts:192-200 (registration)
    Tool registration entry in the listTools response, defining the tool's name, description, and input schema (which is empty as no parameters are required).
    {
      name: 'get_sd_upscalers',
      description: 'Get list of available upscaler models',
      inputSchema: {
        type: 'object',
        properties: {},
        required: []
      }
    },
  • Input schema for the get_sd_upscalers tool, specifying no required properties.
    inputSchema: {
      type: 'object',
      properties: {},
      required: []
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. It doesn't describe whether this is a read-only operation, whether it requires authentication, what format the list returns in, or any rate limits. The description only states what the tool does, not how it behaves.

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, efficient sentence that communicates the essential purpose without any wasted words. It's appropriately sized for a simple list-retrieval tool and front-loads the key information.

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?

For a tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what format the list returns (array of strings? objects with metadata?), whether the list is filtered or complete, or how this tool relates to the sibling 'upscale_images' tool that presumably uses these models.

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

Parameters4/5

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

The tool has zero parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, which is correct for this parameterless tool.

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 clearly states the action ('Get list') and resource ('available upscaler models'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'get_sd_models' or 'upscale_images', but the focus on 'upscaler models' provides reasonable implicit distinction.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention prerequisites, timing considerations, or relationships to sibling tools like 'upscale_images' (which might use these models) or 'get_sd_models' (which appears to serve a similar purpose for different models).

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/Ichigo3766/image-gen-mcp'

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