Skip to main content
Glama

mnemon_admin_reap_branches

Prune orphaned ephemeral sandbox and pull-request branches to reclaim storage extents, with optional dry-run preview and age threshold control.

Instructions

Prune and reclaim storage extents from orphaned ephemeral sandbox or pull-request branches.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mnemon_admin_reap_branches"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNoDry run preview mode without actual extent deletion
max_age_hoursNoReap branches older than this threshold in hours (default: 24)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and only implies destructiveness through 'prune and reclaim'. It never states that extent deletion is irreversible, whether branch metadata is also removed, what permissions are required, or that dry_run exists as a safety path (that lives only in the schema).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, and the operative scope information arrives immediately. It is efficient, though its brevity borders on under-specification for a destructive admin operation.

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

Completeness2/5

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

This is a destructive storage-reclaiming admin tool with no annotations and no output schema, so the description must supply the behavioral context. It omits reversibility, permission requirements, and any indication of what the call reports back, leaving an agent to guess before running an irreversible operation.

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 dry_run and max_age_hours fully documented in the input schema, so the baseline is 3. The description adds no additional meaning about the threshold semantics (e.g. what happens at max_age_hours boundaries) or the effect of preview mode.

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?

The description gives a specific verb pair ('prune and reclaim storage extents') and a precise target set ('orphaned ephemeral sandbox or pull-request branches'), so an agent knows exactly what the tool operates on. It does not differentiate itself from the similarly named sibling thanaton_reap_extents, which an agent could easily confuse with this one.

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?

There is no explicit guidance on when to invoke this versus alternatives, no mention of prerequisites, and no suggestion to run dry_run first before destructive reaping. The word 'orphaned' hints at the trigger condition, but this is scope vocabulary rather than actionable when-to-use instruction.

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