dsh-cli-mcp

Overview Schema Source Related Servers Discussions Admin

dsh

Destructive

Run coding tasks through your local DeepSeek Harness CLI. Provide a self-contained prompt; get stdout, stderr, exit code, and execution time.

Instructions

Run a prompt through your locally installed DeepSeek Harness CLI (dsh --print). Blocks until dsh settles, then returns the captured stdout, the last 4 KB of stderr, the exit code, and the wall-clock time. dsh cannot see this conversation, so the prompt must be self-contained: file paths, goal, constraints, expected output format.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prompt": "<prompt>"
    },
    "name": "dsh"
  }
}

Input Schema

Name	Required	Description
`cwd`	No	Absolute path where dsh will run. Defaults to the server's cwd. Relative paths are rejected.
`prompt`	Yes	The complete task for the DeepSeek Harness agent. Must be self-contained — dsh cannot see your conversation, so include everything it needs (file paths, goal, constraints, expected output format).
`timeout_ms`	No	Wall-clock timeout in milliseconds. Defaults to 300000 (5 min). Hard ceiling is 1800000 (30 min). On timeout, dsh is sent SIGTERM (then SIGKILL after 5 s) and the tool result is reported as a `DshTimeout` error.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The annotations already convey that this is not read-only, is not idempotent, is open-world, and may be destructive. Beyond that, the description adds useful behavioral details: it blocks until dsh settles, returns captured stdout, the last 4 KB of stderr, the exit code, and wall-clock time, and it cannot access the conversation context. These are meaningful additions that help an agent anticipate the tool's runtime behavior and output shape.

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 three tight sentences, front-loaded with the tool's primary action and command, followed by behavioral details and the key prompt constraint. Every sentence adds value and there is no redundancy or filler.

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 tool with no output schema, the description does well by specifying exactly what is returned: stdout, last 4 KB of stderr, exit code, and wall-clock time. It also covers blocking behavior and the important limitation that dsh cannot see the conversation. A small gap is that it does not explicitly mention the timeout escalation behavior in the main description, though that is covered in the timeout parameter schema.

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?

Schema description coverage is 100%, so the schema already fully documents all three parameters. The description reinforces the prompt self-containment requirement but does not materially extend it beyond what the prompt parameter schema already states. This matches the baseline 3 for full schema coverage.

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 states a specific verb and resource: 'Run a prompt through your locally installed DeepSeek Harness CLI (`dsh --print`)'. It clearly identifies what the tool does and even names the underlying command. With no sibling tools to distinguish from, this is unambiguous and fully specific.

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?

There are no sibling tools, so no alternative comparison is needed, but the description gives clear operational context: the tool runs a self-contained prompt through a local CLI and blocks until completion. It also provides a crucial usage constraint: dsh cannot see the conversation, so the prompt must be fully self-contained. It stops short of explicit when-to-use or when-not-to-use guidance, so it earns a 4 rather than a 5.

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

dshA