Skip to main content
Glama

Discard a sandbox

argon_sandbox_discard
DestructiveIdempotent

Delete an Argon sandbox immediately and reclaim its storage. Use it to abandon a sandbox branch when unmerged changes are no longer needed.

Instructions

Delete a sandbox immediately and reclaim its storage. Unmerged changes are lost.

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": {
      "project": "<project>",
      "branch": "<branch>"
    },
    "name": "argon_sandbox_discard"
  }
}

Input Schema

NameRequiredDescriptionDefault
branchYesSandbox branch name
projectYesProject name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered structurally. The description adds genuinely new context: the deletion is immediate, storage is reclaimed, and unmerged work is irrecoverably lost — the last point being the key thing an agent needs before calling.

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 sentences, front-loaded with the action and its effect, then the irreversible consequence. Nothing is padded or repeated from the title.

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 two-parameter destructive tool with full schema coverage and complete annotations, the description supplies what the structured fields cannot: immediacy and data loss. It could go further by noting there is no undo path or pointing at snapshot/keep alternatives, but it is sufficient to call safely.

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% for both parameters (project, branch), so the schema already carries their meaning. The description adds no format, naming, or lookup guidance beyond that, making the baseline 3 appropriate.

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?

States a specific verb (delete) and resource (sandbox) plus the secondary effect of reclaiming storage, which separates it from non-destructive siblings like argon_sandbox_keep. It does not explicitly name an alternative, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'unmerged changes are lost' implies the tool is for sandboxes whose work is disposable, but the description never says when to use this versus argon_sandbox_keep, argon_merge_apply, or argon_snapshot_create. Usage is inferable rather than stated.

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