Skip to main content
Glama
Sign In
sandbox-mcp

sandbox-mcp

by bird
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

kill

Terminate a background process by name or ID within an isolated sandbox, freeing resources and stopping unneeded tasks.

Instructions

Kill a background process.

Args: name: Process name/ID from bg. sandbox: Named sandbox to use (default "default")

Returns: Confirmation.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
sandboxNodefault

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It states 'kill' (a destructive action) and returns confirmation, but does not describe side effects (e.g., what happens if process doesn't exist), reversibility, or permission requirements.

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 extremely concise, using two short sentences plus a parameter list. Every sentence is necessary and front-loaded with the core purpose.

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 simple kill command with an output schema (confirmation), the description is minimally adequate. However, it lacks details on error handling, idempotency, and behavioral edge cases that would be expected given no annotations.

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 description adds meaning beyond the input schema: 'name' is clarified as 'Process name/ID from bg', and 'sandbox' includes a default value and context ('Named sandbox to use'). This compensates for the 0% schema coverage.

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 'Kill a background process' with a specific verb and resource. It distinguishes from sibling tools like 'bg' (which starts background processes) and 'destroy' (which destroys sandboxes), making its purpose unambiguous.

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 is provided on when to use this tool versus alternatives (e.g., when to use 'kill' vs 'destroy' or 'bg'). The description does not mention prerequisites, exclusions, or context-specific advice.

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