Skip to main content
Glama

thanaton_reap_extents

Reclaims unreferenced CoW disk extents and releases host RAM via process_madvise(MADV_DONTNEED), recovering storage and memory from stale copy-on-write data in sandboxes.

Instructions

Autonomous CoW extent reaper: Reclaims unreferenced disk blocks and frees host RAM via process_madvise(MADV_DONTNEED).

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": "thanaton_reap_extents"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavior: it only reclaims *unreferenced* blocks and the RAM effect is achieved through madvise, which usefully signals the operation is non-destructive to live data. It omits whether elevated privileges are required for host-level madvise, whether concurrent runs are safe, whether the operation is interruptible, and what the response contains. That is a meaningful but incomplete behavioral picture for a zero-parameter host-level operation.

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 front-loaded sentence that identifies the tool class first and then the two concrete effects. Every clause adds information; there is no filler or repetition.

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 zero-parameter tool with no output schema, the definition explains the action and mechanism but leaves the scope undefined — with no inputs, an agent cannot tell whether this reaps extents host-wide, per project, or per volume, nor what it gets back. That scoping question is the main gap an agent would need answered before calling it.

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 tool takes no parameters, so the baseline of 4 applies. The description does not need to explain inputs, and it correctly implies the tool is self-directed rather than parameterized.

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 names a specific verb+resource pair: reclaiming unreferenced CoW disk extents and freeing host RAM. The mechanism (process_madvise MADV_DONTNEED) makes the effect unambiguous and clearly distinct from siblings like mnemon_admin_reap_branches. It stops short of explicitly contrasting itself with a named alternative, so it lands at 4 rather than 5.

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 statement of when an agent should invoke this versus other maintenance tools, no prerequisites, and no exclusions. 'Autonomous' hints that it self-selects its target set, but nothing tells the agent under what conditions a reap is appropriate or when it should be avoided.

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