LocalREPL MCP Server

by angrysky56

Overview Schema Source Related Servers Discussions Admin

Python

Local

vacuum_memory

Trim stored data to keep only the newest N rows, freeing disk space and preventing unbounded growth.

Instructions

Keep only the most recent N rows and reclaim disk space. Call occasionally to prevent unbounded growth.

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

Input Schema

Name	Required	Description	Default
`keep_last_n`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 12, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. Description mentions reclaiming disk space and preventing unbounded growth but omits critical behavioral details such as whether the operation is destructive, reversible, blocking, or requires special permissions. This leaves significant ambiguity for a data-modifying tool.

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?

Two short sentences, front-loaded with the main action ('Keep only the most recent N rows'). Every word serves a purpose; no fluff or redundancy.

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 simple maintenance tool with one parameter and no output schema, the description is minimally adequate. However, it lacks context about side effects, blocking behavior, or what 'rows' refers to. Given the sibling tool complexity, a bit more detail would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single parameter 'keep_last_n'. The description does not mention the parameter at all. The parameter name is self-explanatory, but the tool description should at least reference it to clarify its role in the operation, especially with no output 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 the verb 'Keep only the most recent N rows' and the resource 'memory', with specific outcome 'reclaim disk space'. It distinguishes from sibling tools which focus on command execution, REPLs, and shells, making this the only memory management tool.

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?

Description includes 'Call occasionally to prevent unbounded growth', providing clear when-to-use guidance. While it does not explicitly list when not to use, the sibling tools offer no memory management alternatives, so the context is sufficient.

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