Skip to main content
Glama

proc_exec

Execute commands on remote servers via SSH to automate system administration tasks, manage files, install packages, and control services.

Instructions

Executes a command on the remote system

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesSSH session ID
commandYesCommand to execute
cwdNoWorking directory
envNoEnvironment variables

Implementation Reference

  • Handler implementation for 'proc_exec' which calls 'execCommand'.
    case 'proc_exec': {
      const params = ExecSchema.parse(args);
      const result = await execCommand(
        params.sessionId,
        params.command,
        params.cwd,
        params.env as Record<string, string>,
        params.timeoutMs
      );
      // Add safety warning (never blocks, only warns)
      const resultWithWarning = addSafetyWarningToResult(params.command, result);
      logger.info('Command executed', { sessionId: params.sessionId, command: redactSensitiveData(params.command) });
      return { content: [{ type: 'text', text: JSON.stringify(resultWithWarning, null, 2) }] };
    }
  • src/mcp.ts:148-161 (registration)
    Tool registration for 'proc_exec'.
    {
      name: 'proc_exec',
      description: 'Executes a command on the remote system',
      inputSchema: {
        type: 'object',
        properties: {
          sessionId: { type: 'string', description: 'SSH session ID' },
          command: { type: 'string', description: 'Command to execute' },
          cwd: { type: 'string', description: 'Working directory' },
          env: { type: 'object', description: 'Environment variables' }
        },
        required: ['sessionId', 'command']
      }
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this executes a command but doesn't mention critical aspects like whether this requires specific permissions, what happens with errors, if there are timeouts or rate limits, or what the output format looks like. This is inadequate for a tool that performs remote execution.

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 a single, efficient sentence with zero wasted words. It's appropriately sized and front-loaded with the core functionality.

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?

For a remote command execution tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the tool returns, error handling, security implications, or how it differs from similar tools like 'proc_sudo'. Given the complexity and lack of structured data, more context is needed.

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 documents all parameters thoroughly. The description doesn't add any additional meaning about parameters beyond what's in the schema, so it meets the baseline for high schema coverage.

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 'executes' and the resource 'command on the remote system', making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'proc_sudo' which likely also executes commands, so it doesn't reach the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'proc_sudo' or other execution-related tools. It mentions 'remote system' which implies SSH context, but doesn't explicitly state prerequisites or when-not-to-use scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/oaslananka/mcp-ssh-tool'

If you have feedback or need assistance with the MCP directory API, please join our Discord server