Skip to main content
Glama
cacheout-app

cacheout-mcp

Official
by cacheout-app
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

cacheout_memory_intervention

Destructive

Preview and execute memory reclamation on macOS. Use dry-run first to see what will be freed, then confirm to purge cache and reclaim purgeable memory.

Instructions

Execute a memory reclamation intervention on macOS.

IMPORTANT: Always call with confirm=false first to preview what will happen, then call again with confirm=true to execute.

Available interventions:

  • purge: Flush the Unified Buffer Cache (UBC) to reclaim purgeable memory. Works in both standalone and app modes.

  • trigger_pressure_warn: Manual pressure event (app only, not yet available)

  • reduce_transparency: Toggle transparency setting (app only, not yet available)

  • delete_sleepimage: Remove sleepimage file (app only, not yet available)

  • cleanup_snapshots: Clean orphaned APFS snapshots (app only, not yet available)

  • flush_compositor: Display mode toggle (app only, not yet available)

In standalone mode, only 'purge' is supported. In app mode, only 'purge' is currently wired; other interventions will unlock as the CLI surface grows.

The response always includes a capabilities map showing which interventions are available in the current mode.

Args: params: intervention_name, confirm flag, and optional target_pid.

Returns: str: JSON envelope with mode, capabilities, data, partial.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.6/5.0
Behavior5/5

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

Annotations already mark destructiveHint=true; description adds valuable context on dry-run vs execution, mode-dependent availability, and response capabilities map. Fully transparent about side effects and prerequisites.

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?

Well-structured: one-line summary, bold usage note, bullet list, mode details, return info. Front-loaded and concise given complexity; every sentence adds value.

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?

Covers core usage, interventions, modes, and response hints. Lacks error conditions or performance impact notes, but output schema handles return details. Adequately complete for a moderately complex tool.

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?

Although schema description coverage is 0%, the description explains the intervention list, confirm flag purpose, and mode constraints. Target_pid is noted as reserved. Adds meaningful context beyond the schema.

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?

Description clearly states 'Execute a memory reclamation intervention on macOS,' specifying the verb and resource. It distinguishes from sibling tools by focusing on memory purge/reclaim, unlike cache or disk utilities.

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

Usage Guidelines4/5

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

Provides explicit two-step usage pattern (confirm=false then confirm=true) and lists available interventions with mode constraints. However, no direct comparison to sibling tools for when to use this vs alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cacheout-app/cacheout-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server