Skip to main content
Glama
MrGNSS

Desktop Commander MCP

list_sessions

View all active terminal sessions managed by Desktop Commander MCP to monitor and manage running processes on your computer.

Instructions

List all active terminal sessions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the list_sessions tool. It retrieves active terminal sessions from terminalManager and formats a response listing their PID, blocked status, and runtime.
    export async function listSessions() {
      const sessions = terminalManager.listActiveSessions();
      return {
        content: [{
          type: "text",
          text: sessions.length === 0
            ? 'No active sessions'
            : sessions.map(s =>
                `PID: ${s.pid}, Blocked: ${s.isBlocked}, Runtime: ${Math.round(s.runtime / 1000)}s`
              ).join('\n')
        }],
      };
    }
  • Zod schema defining the input arguments for list_sessions, which requires no parameters.
    export const ListSessionsArgsSchema = z.object({});
  • src/server.ts:78-83 (registration)
    Tool registration in the MCP server's listTools response, defining the name, description, and input schema for list_sessions.
    {
      name: "list_sessions",
      description:
        "List all active terminal sessions.",
      inputSchema: zodToJsonSchema(ListSessionsArgsSchema),
    },
  • src/server.ts:228-229 (registration)
    Dispatch logic in the CallToolRequest handler that routes list_sessions calls to the listSessions function.
    case "list_sessions":
      return listSessions();
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'List all active terminal sessions' but lacks behavioral details: it doesn't specify if this is read-only (implied by 'list'), what 'active' means, how sessions are identified, or if there are rate limits or authentication needs. For a tool with no annotations, this leaves significant gaps in understanding its 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 is a single, efficient sentence ('List all active terminal sessions.') that is front-loaded with the core action and resource. There is no wasted text, and it directly communicates the tool's purpose 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 simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states what the tool does but lacks context on behavior, output format, or usage guidelines. For a list operation, more details on what 'active' entails or the structure of returned data would improve completeness, but it's not entirely inadequate for a basic tool.

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 schema description coverage is 100%, so there are no parameters to document. The description does not need to compensate for any gaps, and it appropriately avoids discussing parameters. A baseline of 4 is applied since no parameter information is required or provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List all active terminal sessions' clearly states the verb ('List') and resource ('active terminal sessions'), making the purpose specific and unambiguous. It distinguishes from siblings like list_directory or list_processes by focusing on terminal sessions rather than files or processes.

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 does not mention prerequisites, exclusions, or compare it to sibling tools (e.g., list_processes might overlap with terminal sessions). Without such context, users must infer usage from the tool name alone.

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/MrGNSS/ClaudeDesktopCommander'

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