Skip to main content
Glama
Sign In
mcp-system

mcp-system

by MikeyBeez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

system_exec

Execute system commands with optional working directory and environment variables for automation and control of system operations.

Instructions

Execute a system command

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": "system_exec"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNoWorking directory (optional)
envNoEnvironment variables (optional)
commandYesCommand to execute

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior1/5

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Execute a system command' gives no information about side effects, output, exit codes, security implications, or potential destructive behavior. It merely restates what the name implies.

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

Conciseness3/5

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

The description is a single short sentence, which is concise, but it is also under-specified for such a powerful and potentially dangerous tool. It lacks structure and does not convey any meaningful detail beyond the tool's name.

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

Completeness1/5

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

This is a high-risk tool (arbitrary command execution) with no output schema and no annotations, yet the description does not mention return values, failure modes, working directory behavior, environment handling, or safety warnings. It is seriously incomplete for the complexity involved.

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?

The input schema has 100% description coverage for all three parameters (command, cwd, env), so the schema already provides parameter semantics. The description itself adds no additional parameter context, but the baseline of 3 is appropriate because the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Execute' and resource 'system command', making the tool's basic purpose unambiguous. It does not explicitly distinguish itself from sibling tools like process_kill or env_set, but the generic nature of 'system command' is evident.

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?

There is no guidance on when to use system_exec versus more specific alternatives such as process_kill or env_set. The description provides no context about suitability, prerequisites, or scenarios where this tool is preferred.

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