Skip to main content
Glama

Keep a sandbox

argon_sandbox_keep
Idempotent

Remove a sandbox's TTL to keep it as a permanent branch and prevent MongoDB sandbox changes from expiring before review or merge.

Instructions

Remove a sandbox's TTL, keeping it as a permanent branch.

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_keep"
  }
}

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 declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, and the description is consistent with that: it describes a non-destructive state change that turns a temporary sandbox into a permanent branch. It adds real context beyond the annotations by identifying the mechanism (TTL removal) and the end state, though it doesn't say whether keeping is reversible or what happens to a kept branch afterward.

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?

A single sentence with zero padding, and the operation (TTL removal) is front-loaded ahead of the resulting state. Nothing could be cut without losing information.

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, non-destructive lifecycle tool with full schema coverage and annotations, the description covers the essential behavior. The only meaningful gap is that it doesn't state whether keeping is reversible or what lifecycle consequences a permanent branch carries.

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%, with both project and branch documented in the schema, so the baseline applies. The description adds no meaning about either parameter, such as whether branch accepts a sandbox ID or a branch name.

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-plus-effect ("Remove a sandbox's TTL") and the resulting state ("keeping it as a permanent branch"), which is far more informative than the title's bare "Keep a sandbox". It does not name a sibling such as argon_sandbox_discard to contrast keep-vs-discard, so sibling differentiation is left to inference.

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?

Usage is only implied: an agent can infer this is the tool for preserving a sandbox that would otherwise expire. There is no explicit when-to-use, no statement of when not to use it, and no pointer to argon_sandbox_discard for the opposite outcome.

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