Skip to main content
Glama
es6kr
by es6kr

list_projects

Retrieve all Claude Code projects and their associated session counts for managing conversation sessions.

Instructions

List all Claude Code projects with session counts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/mcp/index.ts:15-20 (registration)
    Registers the 'list_projects' MCP tool. No input schema. The handler runs session.listProjects() and returns the result as formatted JSON text in MCP content format.
    server.tool('list_projects', 'List all Claude Code projects with session counts', {}, async () => {
      const result = await Effect.runPromise(session.listProjects)
      return {
        content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
      }
    })
  • The main handler logic for listing projects: checks if sessions directory exists, reads directories, counts .jsonl session files in each project directory concurrently.
    export const listProjects = Effect.gen(function* () {
      const sessionsDir = getSessionsDir()
    
      const exists = yield* Effect.tryPromise(() =>
        fs
          .access(sessionsDir)
          .then(() => true)
          .catch(() => false)
      )
    
      if (!exists) {
        return [] as Project[]
      }
    
      const entries = yield* Effect.tryPromise(() => fs.readdir(sessionsDir, { withFileTypes: true }))
    
      const projects = yield* Effect.all(
        entries
          .filter((e) => e.isDirectory())
          .map((entry) =>
            Effect.gen(function* () {
              const projectPath = path.join(sessionsDir, entry.name)
              const files = yield* Effect.tryPromise(() => fs.readdir(projectPath))
              const sessionFiles = files.filter((f) => f.endsWith('.jsonl'))
    
              return {
                name: entry.name,
                path: projectPath,
                sessionCount: sessionFiles.length,
              } satisfies Project
            })
          ),
        { concurrency: 10 }
      )
    
      return projects
    })
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. While 'List' implies a read-only operation, the description doesn't specify whether this requires authentication, how results are paginated, what format the session counts are in, or whether there are rate limits. This leaves significant behavioral questions unanswered.

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 core functionality without any wasted words. It's appropriately sized for a simple listing tool and front-loads the essential information.

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 has no parameters, no annotations, and no output schema, the description provides the minimum viable information about what the tool does. However, it doesn't explain what format the results will be in (projects with session counts), whether there are limitations, or how this relates to other session management tools. For a tool in a complex session management context, more completeness would be helpful.

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 schema already fully documents the parameter situation. The description appropriately doesn't mention parameters, which is correct for a parameterless tool. Baseline would be 4 for zero parameters.

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 with a specific verb ('List') and resource ('Claude Code projects'), and includes additional scope ('with session counts'). However, it doesn't explicitly differentiate from sibling tools like 'list_sessions', which might cause confusion about the resource hierarchy.

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. With sibling tools like 'list_sessions' and 'get_session_files', there's no indication of whether this is a higher-level aggregation tool or how it relates to other listing operations.

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/es6kr/claude-sessions-mcp'

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