Skip to main content
Glama
Sign In
declaw-mcp-server

declaw-mcp-server

Official
by declaw-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

kill_sandbox

Stop a running sandbox and release its resources to clean up after code execution.

Instructions

Destroy a sandbox and release its resources.

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

Input Schema

NameRequiredDescriptionDefault
sandbox_idYesSandbox ID to destroy

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior3/5

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

The description discloses the core destructive behavior and that resources are released, which is essential. However, with no annotations provided, it does not mention irreversibility, potential failure modes, or effects on running processes. The word 'Destroy' implies finality, but richer context would strengthen this.

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?

One concise sentence that is front-loaded and contains no filler. Every word contributes to understanding the tool's purpose.

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

Completeness4/5

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

For a single-parameter destruction tool with no output schema, the description covers the essential action and outcome. It could mention error handling or whether the operation is idempotent, but the simplicity of the tool allows for adequate completeness.

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 already documents sandbox_id with a clear description, and coverage is 100%. The tool description adds no additional parameter meaning, so the baseline of 3 applies.

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 uses a specific verb 'Destroy' with a clear resource 'sandbox', immediately distinguishing it from sibling tools like create_sandbox and list_sandboxes. The phrase 'release its resources' adds additional clarity about what destruction entails.

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 given on when this tool should be used versus alternatives, nor are any prerequisites or exclusions mentioned. The description simply states what it does, leaving the agent to infer that it is for decommissioning sandboxes.

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