Skip to main content
Glama
wonderwhy-er

Claude Desktop Commander MCP

by wonderwhy-er
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

interact_with_process

Destructive

Send input to an existing terminal or REPL and return newly available output, enabling interactive shells, REPL sessions, database consoles, and long-running commands to continue and respond.

Instructions

                    Send input to an existing terminal or REPL process and return newly available output.
                    
                    Useful for interactive shells, Python/Node/R/Julia REPLs, database consoles,
                    and long-running commands started with start_process().
                    
                    Examples:
                    - Interactive Python REPL sessions can be started with `python3 -i`.
                    - Existing interactive sessions accept additional input such as imports or analysis commands.
                    - Interactive sessions can return newly available output while they remain active.
                    
                    SMART DETECTION:
                    - Automatically waits for a recognized prompt when requested
                    - Detects errors and completion states
                    - Early exit prevents unnecessary waiting
                    - Cleans common REPL prompt text from returned output
                    
                    PARAMETERS:
                    - pid: Process ID returned by start_process
                    - input: Text or command to send to the process
                    - timeout_ms: Maximum wait time (default: 8000ms)
                    - wait_for_prompt: Whether to wait for a prompt before returning (default: true)
                    - verbose_timing: Include detailed timing telemetry (default: false)

                    Returns execution result with status indicators.

                    PERFORMANCE DEBUGGING (verbose_timing parameter):
                    When enabled, detailed timing includes:
                    - Exit reason
                    - Total duration and time to first output
                    - Timeline of output events

                    This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pidYes
inputYes
timeout_msNo
verbose_timingNo
wait_for_promptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.17
    • addedInput schema / properties / verbose_timing
      Added value: +{
+  "type": "boolean"
+}
  2. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered. The description adds substantial behavioral context beyond that: smart prompt-waiting, error/completion detection, early exit, prompt-text cleaning, and verbose timing telemetry. It does not itself warn that arbitrary input can be destructive, but the annotation carries that.

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?

Front-loaded with purpose, then organized under SMART DETECTION, PARAMETERS, and PERFORMANCE DEBUGGING headers, which is easy to scan. Minor waste exists: the example bullets partly restate the 'useful for' sentence, and the trailing 'DC: ...' branding line adds no invocation value.

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?

No output schema exists, and the return description ('execution result with status indicators') is thin, but the smart-detection section compensates by explaining cleaned output, error detection, and early exit. For a 5-param interactive mutation tool with annotations covering safety, this is close to complete.

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?

Schema description coverage is 0%, so the description must carry the load, and it does: it documents all five parameters (pid, input, timeout_ms, wait_for_prompt, verbose_timing) and gives defaults (8000ms, true, false) plus semantics for each. The pid is tied back to start_process, which adds real meaning.

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?

States a specific verb and resource ('Send input to an existing terminal or REPL process and return newly available output') and distinguishes itself from the sibling start_process() it depends on. An agent can tell it apart from read_process_output and start_process without opening any schema.

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?

Gives clear context for when to use it: interactive shells, Python/Node/R/Julia REPLs, database consoles, and long-running commands started with start_process(). It names the prerequisite (start_process) but offers no explicit when-not guidance or alternatives (e.g., read_process_output for passive reading).

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

Deploy Server

Other Tools