Txa_MCP

Overview Schema Source Related Servers Discussions Admin

run_shell

Run PowerShell commands safely in your Windows project. Avoids bash/linux syntax for reliable execution in AI IDE environments.

Instructions

Run shell command safely in project. IMPORTANT: OS is WINDOWS, use standard POWERSHELL syntax. Avoid bash/linux commands.

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_shell"
  }
}

Input Schema

Name	Required	Description	Default
`command`	Yes	POWERSHELL command to run

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.0.3Aug 11, 2026

TDQS

A4.1/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds important context about the operating system and syntax, but the term 'safely' is undefined, and there is no information about output format, error handling, side effects, or execution environment beyond the OS.

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 exceptionally concise, consisting of two sentences that front-load the purpose and then deliver a critical usage constraint. Every word earns its place with no redundancy or filler.

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?

For a single-parameter tool, the description is reasonably complete in terms of syntax, but it lacks details about what the tool returns, whether it blocks, or what 'safely' means in practice. Without an output schema or annotations, this creates a moderate gap in the agent's ability to predict the tool's behavior.

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 schema already describes 'command' as a string, so the baseline is 3. The description adds meaningful semantic guidance by specifying PowerShell syntax and warning against bash/linux commands, which directly informs how to construct the command parameter.

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 the tool's action ('Run shell command') and its scope ('in project'), making it distinct from sibling tools like read_file or system_info. The additional note about Windows/PowerShell syntax further clarifies the intended usage environment.

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 description provides concrete usage context by specifying that the OS is Windows and PowerShell syntax is required, with an explicit warning to avoid bash/linux commands. It does not explicitly mention alternatives or when-not-to-use, but the guidance is clear enough for most scenarios.

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