Skip to main content
Glama
Sign In
SapperMCP

SapperMCP

by MasterX1582
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Start Process

start_process

Start a detached background shell command for non-interactive tasks, with optional working directory and environment variables. Use a shell session when interaction or output capture is needed.

Instructions

Start a detached background process (shell command line).

For interactive processes or output capture, use start_shell_session.

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

Input Schema

NameRequiredDescriptionDefault
cwdNo
envNo
commandYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load; "detached" usefully signals the call returns immediately and produces no captured output, which is real information an agent cannot get elsewhere. However, it says nothing about shell interpretation of the command, environment inheritance, default working directory, or whether the spawned process is later reachable via kill_process.

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?

Two short sentences, zero filler, with the core behavior front-loaded and the disambiguation trailing it. Nothing is redundant with the title or with structured fields.

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?

An output schema exists, so return values need not be described, and the purpose-plus-alternative framing covers the selection problem. But for a three-parameter process-spawning tool with no annotations and 0% schema coverage, the description leaves cwd, env, and shell semantics entirely undocumented, which is a meaningful gap before invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description is the only source of meaning and it explains none of them. It never states that cwd sets the working directory or that env overrides/adds environment variables, nor does it clarify how command is quoted or whether it runs through a shell.

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?

States a specific verb and resource ("Start a detached background process") plus the concrete form of the input ("shell command line"), and explicitly names the sibling start_shell_session as the contrasting tool. An agent can distinguish this from start_shell_session without opening either schema.

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?

Gives an explicit routing rule: use start_shell_session for interactive processes or output capture, which implies this tool is for fire-and-forget commands. It does not mention related lifecycle siblings such as wait_for_process, get_process_info, or kill_process, so the agent gets the entry-point decision but not the follow-up path.

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