Skip to main content
Glama

mnemon_autofreeze_policy

Configure automatic zero-CPU freezing of idle instances after a set timeout, keeping the PostgreSQL shared buffer pool in RAM.

Instructions

Configure automatic zero-CPU instance freezing via cgroups v2 (cgroup.freeze) while keeping PostgreSQL shared buffer pool in RAM.

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_id": "<project_id>"
    },
    "name": "mnemon_autofreeze_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesMnemon project / tenant ID
idle_timeout_secondsNoInactivity seconds before auto-freezing (default: 30)
preserve_buffer_poolNoPreserve shared buffers in RAM (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.2/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 meaningful behavior: instances are frozen to zero CPU while the PostgreSQL shared buffer pool stays resident in RAM. However, it says nothing about whether the policy applies immediately or to future idle periods, whether changes are reversible, what permissions are required, or what effect freezing has on in-flight connections.

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; the core purpose leads and the mechanism follows. The cgroups v2 detail earns its place by explaining how freezing is achieved, though it is slightly technical for a purpose statement.

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 configuration-mutation tool with no annotations and no output schema, the description covers what is being changed but not the operational envelope: permanence of the policy, rollback, or effect on running workloads. It is adequate to call the tool but leaves real gaps for an agent reasoning about consequences.

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%, so each parameter is already documented in the schema, and the description adds only conceptual framing (zero-CPU freezing linked to buffer-pool preservation). It does not add format, units, or boundary details beyond what the schema provides, so the baseline 3 applies.

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 (Configure) and a specific resource (automatic zero-CPU instance freezing), plus the underlying mechanism (cgroups v2 cgroup.freeze). It is clearly distinguishable from siblings like mnemon_configure_pooler or mnemon_configure_scaling, though it does not explicitly name a sibling it is not.

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 when-to-use guidance, no conditions under which this should be preferred over mnemon_configure_scaling, and no exclusions or prerequisites stated as requirements. The cgroups v2 mention implies a platform prerequisite but is presented as implementation detail rather than a condition for use.

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