Skip to main content
Glama
MrGNSS

Desktop Commander MCP

by MrGNSS

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();

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
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. It states it lists 'active' sessions, implying a read-only operation, but doesn't specify what 'active' means, whether it requires permissions, how results are formatted, or if there are rate limits. This leaves significant gaps for a tool with zero annotation coverage.

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 directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, with every word earning its place.

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 low complexity (0 parameters, no output schema) and no annotations, the description is minimally adequate. It specifies the resource ('active terminal sessions'), but lacks details on behavior, output format, or usage context, leaving room for improvement in completeness.

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 with 100% schema description coverage, so the schema fully documents the absence of inputs. The description adds no parameter information, but with no parameters, the baseline is 4 as it doesn't need to compensate for gaps.

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 the resource 'active terminal sessions', providing a specific action and target. However, it doesn't differentiate from sibling tools like 'list_processes' or 'list_directory' beyond the resource type, missing explicit sibling distinction.

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 'list_processes' or 'list_directory'. It lacks context about prerequisites, exclusions, or specific scenarios where listing sessions is preferred over other listing tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.