Skip to main content
Glama
nickbaumann98

EverArt Forge MCP Server

list_images

Retrieve all stored images from the EverArt Forge MCP Server to manage and access generated AI artwork.

Instructions

List all stored images

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main handler for the 'list_images' tool. Lists images from storage directory using listStoredImages helper, groups by file type, formats a detailed text response with counts and recent file URLs.
    case "list_images": {
      try {
        const files = await listStoredImages();
        if (files.length === 0) {
          return {
            content: [{ type: "text", text: "No stored images found. Try generating some images first!" }],
          };
        }
    
        // Group files by type for better display
        const filesByType: Record<string, string[]> = {};
        
        for (const file of files) {
          const ext = path.extname(file).slice(1).toLowerCase();
          if (!filesByType[ext]) {
            filesByType[ext] = [];
          }
          filesByType[ext].push(file);
        }
        
        let resultText = "šŸ“ Stored images:\n\n";
        
        for (const [type, typeFiles] of Object.entries(filesByType)) {
          resultText += `${type.toUpperCase()} Files (${typeFiles.length}):\n`;
          resultText += typeFiles.map(f => `• ${f}`).join("\n");
          resultText += "\n\n";
        }
        
        resultText += `Total: ${files.length} file(s)`;
        
        // Add file URLs instead of trying to embed images
        const recentFiles = files.slice(-5);
        const fileUrls: string[] = [];
        
        for (const file of recentFiles) {
          const filepath = path.join(STORAGE_DIR, file);
          fileUrls.push(`file://${filepath}`);
        }
        
        return {
          content: [
            { type: "text", text: resultText },
            ...(fileUrls.length > 0 ? [{ 
              type: "text", 
              text: "\nRecent images:\n" + fileUrls.map(url => `• ${url}`).join('\n')
            }] : []),
          ],
        };
      } catch (error: unknown) {
        const errorMessage = error instanceof Error ? error.message : "Unknown error";
        return errorResponse({
          type: EverArtErrorType.STORAGE_ERROR,
          message: `Error listing images: ${errorMessage}`
        });
      }
    }
  • Helper function that reads the STORAGE_DIR and returns an array of image files matching supported extensions (svg, png, jpg, jpeg, webp). Handles missing directory gracefully.
    async function listStoredImages(): Promise<string[]> {
      try {
        const files = await fs.readdir(STORAGE_DIR);
        return files.filter((file: string) => /\.(svg|png|jpe?g|webp)$/i.test(file));
      } catch (error) {
        if ((error as NodeJS.ErrnoException).code === "ENOENT") {
          return [];
        }
        throw error;
      }
    }
  • src/index.ts:420-426 (registration)
    Tool registration in the ListToolsRequestSchema response, including name, description, and empty inputSchema (no parameters required).
      name: "list_images",
      description: "List all stored images",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Input schema for list_images tool: 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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('List all stored images') but doesn't describe what 'List' entails—such as whether it returns metadata, thumbnails, or full images; if there's pagination or filtering; or any performance or rate-limiting considerations. This leaves significant gaps in understanding the tool's behavior.

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 'List all stored images' is extremely concise—a single, clear sentence with no wasted words. It's front-loaded and efficiently communicates the core action without any fluff, making it easy for an agent to parse quickly.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimal but insufficient. It doesn't explain what 'List' returns (e.g., a list of image IDs, metadata, or URLs), which is critical for a tool with no output schema. For a basic list operation, more context on the return format is needed to be complete.

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 input schema has 0 parameters with 100% coverage, so the schema fully documents the lack of inputs. The description doesn't add parameter details beyond this, but since there are no parameters to explain, it doesn't need to compensate. A baseline of 4 is appropriate as the description doesn't contradict or add unnecessary information.

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 all stored images' clearly states the verb ('List') and resource ('stored images'), making the tool's purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'view_image' (which might show a single image) or 'generate_image' (which creates new images), so it doesn't reach the highest score.

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 like 'view_image' or 'generate_image'. It doesn't mention any prerequisites, exclusions, or contextual factors that would help an agent choose between these tools, leaving the usage unclear.

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/nickbaumann98/everart-forge-mcp'

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