Skip to main content
Glama

list_supported_formats

Lists all image formats supported for conversion, including JPG, PNG, WebP, GIF, BMP, TIFF, SVG, ICO, and AVIF.

Instructions

列出支持的图片格式

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler for 'list_supported_formats' that invokes the ImageConverter's getSupportedFormats() method and formats the response as text content listing input and output formats.
    case 'list_supported_formats': {
      const formats = this.converter.getSupportedFormats();
      return {
        content: [
          {
            type: 'text',
            text: `支持的图片格式:\n输入格式:${formats.input.join(', ')}\n输出格式:${formats.output.join(', ')}`
          }
        ]
      };
    }
  • Core helper method that returns the object containing arrays of supported input and output image formats.
    getSupportedFormats() {
      return {
        input: this.supportedInputFormats,
        output: this.supportedOutputFormats
      };
    }
  • Class properties defining the lists of supported input and output image formats used by getSupportedFormats().
    private supportedInputFormats = [
      'jpg', 'jpeg', 'png', 'gif', 'bmp', 'tiff', 'tif', 
      'webp', 'svg', 'ico', 'psd', 'heic', 'heif', 'avif'
    ];
    
    private supportedOutputFormats = [
      'jpg', 'jpeg', 'png', 'gif', 'bmp', 'tiff', 'webp', 
      'svg', 'ico', 'avif'
    ];
  • src/index.ts:191-197 (registration)
    Tool registration in the ListTools response, including name, description, and empty input schema (no parameters required).
      name: 'list_supported_formats',
      description: '列出支持的图片格式',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    }
  • Input schema definition for the tool: an empty object since no parameters are needed.
    inputSchema: {
      type: 'object',
      properties: {}
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states what the tool does ('列出支持的图片格式') without any behavioral traits such as whether it requires authentication, has rate limits, returns a static list or dynamic data, or how the output is structured. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 directly states the tool's purpose with zero waste. It is appropriately sized and front-loaded, making it easy to understand at a glance without unnecessary elaboration.

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

Completeness3/5

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

Given the tool's low complexity (0 parameters, no annotations, no output schema), the description is minimally complete. It states the purpose clearly but lacks behavioral context (e.g., output format, authentication needs) and usage guidelines. For a simple list tool, this is adequate but leaves gaps that could hinder an AI agent's effective use, especially without annotations to compensate.

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 0 parameters, and the schema description coverage is 100% (as there are no parameters to describe). The description doesn't need to add parameter semantics beyond the schema, so it meets the baseline of 4 for tools with no parameters, as it doesn't introduce any confusion or redundancy regarding inputs.

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 '列出支持的图片格式' (List supported image formats) clearly states the tool's purpose with a specific verb ('列出' - list) and resource ('支持的图片格式' - supported image formats). It distinguishes from siblings like 'batch_convert_images' and 'convert_image' which perform conversions rather than listing formats. However, it doesn't explicitly differentiate from 'get_image_info' which might provide format information for specific images.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to use it (e.g., before conversion to check compatibility) or when not to use it (e.g., for getting format info about a specific image). There's no reference to sibling tools like 'get_image_info' for comparison, leaving usage context implied at best.

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/pickstar-2002/image-mcp'

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