Skip to main content
Glama
Sign In

Remote Desktop Commander

by app.desktopcommander
OverviewDiscussionsAdmin

list_sessions

Read-only
                    List all active terminal sessions.
                    
                    Shows session status including:
                    - PID: Process identifier  
                    - Blocked: Whether session is waiting for input
                    - Runtime: How long the session has been running
                    
                    DEBUGGING REPLs:
                    - "Blocked: true" often means REPL is waiting for input
                    - Use this to verify sessions are running before sending input
                    - Long runtime with blocked status may indicate stuck process
                    
                    This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.

Input Schema

NameRequiredDescriptionDefault
deviceIdNoThe ID of the device to run this tool on (from list_devices). Required when more than one device is online; may be omitted when only one device is connected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With readOnlyHint/destructiveHint/openWorldHint already declaring the safety profile, the description adds real interpretive context: it explains what "Blocked: true" signifies and that long runtime plus blocked may mean a stuck process. It omits pagination/result-size behavior, but for a session listing this is a meaningful value-add beyond the annotations.

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

Conciseness4/5

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

Purpose is stated up front and the field list plus debugging tips are scannable bullet points that each earn their place. The trailing "DC: ..." aliasing note is invocation trivia that dilutes focus slightly, and the leading indentation is sloppy but harmless.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, zero-required-parameter listing tool with full annotation coverage and no output schema, the description covers purpose, returned fields, and interpretation adequately. Only the optional deviceId trigger and behavior on larger result sets go unmentioned, both minor.

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?

There is one optional parameter (deviceId) with 100% schema description coverage that already explains it comes from list_devices and is only needed with multiple devices online. The description does not mention deviceId at all, so it adds nothing here, but the schema carries the load and baseline 3 applies.

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?

"List all active terminal sessions" gives a specific verb and resource, and the enumerated return fields (PID, Blocked, Runtime) pin down that this is about interactive terminal sessions rather than OS processes, distinguishing it from the sibling list_processes. An agent can tell at a glance which listing tool it needs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The DEBUGGING REPLs block gives explicit usage context: "Use this to verify sessions are running before sending input" and how to read a blocked/long-runtime state. It names the downstream action (sending input) rather than a sibling tool name, so the routing to interact_with_process is implied rather than explicit.

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

All Remote Desktop Commander toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources