Coding Agent MCP Server

by Sukarth

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

run_command_stream

Execute a command and stream its output in real-time, enabling immediate monitoring of progress and results.

Instructions

Execute a command and stream output in real-time

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": {
      "command": "<command>"
    },
    "name": "run_command_stream"
  }
}

Input Schema

Name	Required	Description	Default
`command`	Yes	Command to execute
`workingDirectory`	No	Working directory for command execution	.
`timeout`	No	Command timeout in milliseconds

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1May 29, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations exist, so description carries full burden. It mentions streaming but does not disclose safety concerns (e.g., arbitrary command execution), what 'output' includes (stdout/stderr), or whether streaming is to console or returned. Minimal behavioral info.

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?

Single sentence with key differentiator front-loaded. No wasted words, but slightly too brief given tool complexity. Still efficient.

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

Completeness2/5

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

Tool complexity is moderate (command execution with streaming), but description lacks details on behavior (return type, error handling, streaming semantics). No output schema. Incomplete for safe and effective use.

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 coverage is 100% with descriptions for all parameters. The description adds no additional info beyond the schema, so baseline score of 3 is appropriate.

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 clearly states it executes a command and streams output in real-time, which distinguishes it from sibling tool 'run_command'. The verb 'execute' and resource 'command' are specific.

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?

No guidance on when to use this tool versus alternatives (e.g., 'run_command'). No prerequisites, exclusions, or context for when streaming is appropriate are provided.

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