Skip to main content
Glama

list_projects

Retrieve and overview all projects by specifying a working directory. Access comprehensive details, progress insights, and project-specific storage for efficient tracking and navigation within your workspace.

Instructions

Discover and overview all your projects with comprehensive details and progress insights. Perfect for getting a bird's-eye view of your work portfolio, tracking project status, and quickly navigating between different initiatives in your workspace with project-specific storage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workingDirectoryYesThe full absolute path to the working directory where data is stored. MUST be an absolute path, never relative. Windows: "C:\Users\username\project" or "D:\projects\my-app". Unix/Linux/macOS: "/home/username/project" or "/Users/username/project". Do NOT use: ".", "..", "~", "./folder", "../folder" or any relative paths. Ensure the path exists and is accessible before calling this tool. NOTE: When server is started with --claude flag, this parameter is ignored and a global user directory is used instead.

Implementation Reference

  • The createListProjectsTool function defines the core handler logic for the 'list_projects' tool. It fetches all projects from storage, formats them with name, ID, description, and timestamps, handles empty list and errors, and returns formatted text content.
    export function createListProjectsTool(storage: Storage) {
      return {
        name: 'list_projects',
        description: 'View all projects in the task management system',
        inputSchema: {},
        handler: async () => {
          try {
            const projects = await storage.getProjects();
    
            if (projects.length === 0) {
              return {
                content: [{
                  type: 'text' as const,
                  text: 'No projects found. Create your first project to get started!'
                }]
              };
            }
    
            const projectList = projects.map(project => {
              return `**${project.name}** (ID: ${project.id})
    Description: ${project.description}
    Created: ${new Date(project.createdAt).toLocaleString()}
    Updated: ${new Date(project.updatedAt).toLocaleString()}`;
            }).join('\n\n');
    
            return {
              content: [{
                type: 'text' as const,
                text: `Found ${projects.length} project(s):\n\n${projectList}`
              }]
            };
          } catch (error) {
            return {
              content: [{
                type: 'text' as const,
                text: `Error listing projects: ${error instanceof Error ? error.message : 'Unknown error'}`
              }],
              isError: true
            };
          }
        }
      };
    }
  • src/server.ts:76-97 (registration)
    Registers the 'list_projects' tool on the MCP server. Includes input schema requiring 'workingDirectory', detailed description, and wrapper handler that initializes storage and invokes the core tool handler.
    server.tool(
      'list_projects',
      'Discover and overview all your projects with comprehensive details and progress insights. Perfect for getting a bird\'s-eye view of your work portfolio, tracking project status, and quickly navigating between different initiatives in your workspace with project-specific storage.',
      {
        workingDirectory: z.string().describe(getWorkingDirectoryDescription(config))
      },
      async ({ workingDirectory }: { workingDirectory: string }) => {
        try {
          const storage = await createStorage(workingDirectory, config);
          const tool = createListProjectsTool(storage);
          return await tool.handler();
        } catch (error) {
          return {
            content: [{
              type: 'text' as const,
              text: `Error: ${error instanceof Error ? error.message : 'Unknown error'}`
            }],
            isError: true
          };
        }
      }
    );
  • Input schema for the 'list_projects' tool, defining the required 'workingDirectory' parameter with Zod validation and description.
    {
      workingDirectory: z.string().describe(getWorkingDirectoryDescription(config))
    },
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. While it mentions 'comprehensive details and progress insights' and 'quickly navigating between different initiatives', it doesn't specify what data is returned, whether there's pagination, what format the output takes, or any rate limits. For a list operation with zero annotation coverage, this leaves significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences but contains marketing language like 'Perfect for getting a bird's-eye view' and 'quickly navigating between different initiatives' that don't add operational clarity. The first sentence could be more direct, and the second sentence mixes purpose with implementation details about 'project-specific storage'.

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 list operation with no annotations and no output schema, the description should provide more complete context about what data is returned, how results are structured, and any limitations. The current description focuses on benefits rather than operational details, leaving significant gaps for an AI agent to understand what this tool actually returns.

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 description provides no information about the single required parameter (workingDirectory), but the schema has 100% description coverage with detailed examples and constraints. According to the rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no parameter information in the description.

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 tool's purpose as discovering and overviewing projects with comprehensive details and progress insights, which is a specific verb+resource combination. However, it doesn't explicitly distinguish this from sibling tools like 'get_project' or 'create_project', which would be needed for a perfect 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 mentions this is 'perfect for getting a bird's-eye view' and 'tracking project status', but provides no explicit guidance on when to use this tool versus alternatives like 'get_project' for individual projects or 'list_tasks' for task-level views. There's no mention of prerequisites or when-not-to-use scenarios.

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/Pimzino/agentic-tools-mcp'

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