Skip to main content
Glama
cacheout-app

cacheout-mcp

Official
by cacheout-app

cacheout_get_recommendations

Read-onlyIdempotent

Retrieve predictive memory health recommendations from the Cacheout engine, covering compressor degradation, swap pressure, high-growth processes, and agent memory pressure.

Instructions

Get predictive memory recommendations from the Cacheout engine.

Returns advisory recommendations about memory health, including compressor degradation, swap pressure, high-growth processes, Rosetta-translated processes, and agent memory pressure.

Mode-dependent behavior:

  • socket: Full recommendations from daemon (all 7 types when conditions apply)

  • app: Snapshot-only recommendations from CLI (no trend-based types)

  • standalone: Basic recommendations from sysctl (compressor_low_ratio, swap_pressure only)

The partial flag in _meta indicates degraded results:

  • Always true in app/standalone modes (no trend data)

  • True in socket mode only when daemon's process scan was incomplete

Returns: str: JSON with recommendations array and _meta. { "recommendations": [ { "type": "compressor_low_ratio", "message": "Compression ratio 1.5 is below 2.0", "process": null, "pid": null, "impact_value": 1.5, "impact_unit": "ratio", "confidence": "low", "source": "standalone" } ], "_meta": { "mode": "standalone", "count": 1, "partial": true, "source": "standalone" } }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint. The description adds valuable behavioral context: mode-dependent result quality, the meaning of the partial flag, and the list of recommendation types. No contradictions with annotations.

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?

The description is well-structured: starts with overall purpose, then details mode behavior, partial flag, and includes an example output. Every sentence serves a purpose, no fluff. It is front-loaded and appropriately sized.

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

Completeness5/5

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

Given the tool's complexity (multiple modes, partial flag, structured output), the description covers all essential aspects: mode-dependent behavior, partial flag semantics, and a full output schema example. It is complete enough for an agent to use correctly.

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?

There are no parameters, and schema description coverage is 100%. The description adds context about return format and mode-dependent behavior, which compensates for the lack of parameters. Baseline 4 for zero parameters is appropriate.

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?

The description clearly states the tool gets predictive memory recommendations from the Cacheout engine, listing specific recommendation types. This verb+resource combination distinguishes it from siblings like cacheout_get_memory_stats or cacheout_get_compressor_health.

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?

The description explains mode-dependent behavior (socket, app, standalone) and when the partial flag is true, giving the agent context on when results are degraded. It does not explicitly compare to siblings or state when not to use, but the mode details provide sufficient guidance.

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