Skip to main content
Glama

superdesign_list

View all designs in your workspace to manage and organize UI components, wireframes, and visual assets created with the design orchestrator.

Instructions

List all created designs in the workspace

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspace_pathNoWorkspace path (defaults to current directory)

Implementation Reference

  • Handler function for superdesign_list tool that lists design files in the superdesign/design_iterations and design_system directories, formats a text response with file lists.
    case "superdesign_list": {
        const { workspace_path } = ListDesignsSchema.parse(args);
        try {
            const superdesignDir = getSuperdeignDirectory(workspace_path);
            const designIterationsDir = path.join(superdesignDir, 'design_iterations');
            const designSystemDir = path.join(superdesignDir, 'design_system');
            const designFiles = await glob('*.{html,svg}', { cwd: designIterationsDir });
            const systemFiles = await glob('*.json', { cwd: designSystemDir });
            let result = `Superdesign workspace: ${superdesignDir}\n\n`;
            if (designFiles.length > 0) {
                result += `Design iterations (${designFiles.length}):\n`;
                designFiles.forEach(file => {
                    result += `  - ${file}\n`;
                });
            }
            else {
                result += "No design iterations found.\n";
            }
            result += "\n";
            if (systemFiles.length > 0) {
                result += `Design systems (${systemFiles.length}):\n`;
                systemFiles.forEach(file => {
                    result += `  - ${file}\n`;
                });
            }
            else {
                result += "No design systems found.\n";
            }
            return {
                content: [{ type: "text", text: result }],
            };
        }
        catch (error) {
            return {
                content: [{ type: "text", text: `Error listing designs: ${error.message}` }],
            };
        }
    }
  • Zod schema for validating input parameters of the superdesign_list tool (workspace_path optional).
    const ListDesignsSchema = z.object({
        workspace_path: z.string().optional().describe("Workspace path (defaults to current directory)")
    });
  • Registration of the superdesign_list tool in the listTools response, including name, description, and input schema.
    {
        name: "superdesign_list",
        description: "List all created designs in the workspace",
        inputSchema: {
            type: "object",
            properties: {
                workspace_path: { type: "string", description: "Workspace path (defaults to current directory)" }
            },
        },
    },
  • Helper function to get or create the superdesign directory structure including design_iterations and design_system subdirectories.
    function getSuperdeignDirectory(workspacePath) {
        const basePath = workspacePath || process.cwd();
        const superdesignDir = path.join(basePath, 'superdesign');
        if (!existsSync(superdesignDir)) {
            mkdirSync(superdesignDir, { recursive: true });
        }
        const designIterationsDir = path.join(superdesignDir, 'design_iterations');
        if (!existsSync(designIterationsDir)) {
            mkdirSync(designIterationsDir, { recursive: true });
        }
        const designSystemDir = path.join(superdesignDir, 'design_system');
        if (!existsSync(designSystemDir)) {
            mkdirSync(designSystemDir, { recursive: true });
        }
        return superdesignDir;
    }
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 mentions listing designs but doesn't cover critical aspects like whether this is a read-only operation, pagination behavior, error conditions, or performance characteristics. For a list tool with zero annotation coverage, this leaves significant gaps.

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 states the tool's purpose without any unnecessary words. It's appropriately sized for a simple list operation and front-loaded with the essential 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?

Given the lack of annotations and output schema, the description is insufficiently complete. It doesn't explain what the return format looks like (e.g., list of design objects, pagination details), error handling, or how it differs from similar sibling tools. For a tool with no structured metadata, the description should provide more context.

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%, with the single parameter 'workspace_path' well-documented in the schema. The description doesn't add any additional parameter information beyond what the schema already provides, so it meets the baseline score when the schema does the heavy lifting.

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 verb ('List') and resource ('all created designs in the workspace'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'superdesign_gallery' which might also list designs, 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?

No guidance is provided on when to use this tool versus alternatives like 'superdesign_gallery' or 'superdesign_check_files'. The description only states what it does, not when it's appropriate or what prerequisites might exist.

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/jonthebeef/superdesign-mcp-claude-code'

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