Skip to main content
Glama
Sign In
Loom

Loom

by MlkBlk-IT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Ctx Vacuum

ctx_vacuum
Idempotent

Run SQLite VACUUM to reclaim unused space and reduce database file size.

Instructions

Run SQLite VACUUM to reclaim unused space.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the description adds nothing on safety. VACUUM is a heavy, potentially long-running, exclusive-lock operation that can require free disk roughly equal to the database size; none of that cost or blocking behavior is disclosed, which matters for an agent deciding when to call it.

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 short sentence that front-loads the underlying operation and its purpose; nothing is redundant or padded.

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?

With zero parameters, full schema coverage, and an output schema, the description covers the essentials an agent needs before invoking. The one gap is operational: it never says the operation can be slow or exclusive, which is the main risk factor for a maintenance call.

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 zero parameters and closes the schema with additionalProperties=false, so there is no parameter meaning for the description to add. The baseline for a 0-parameter tool 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?

States a specific verb ('Run ... VACUUM') and resource (SQLite database) plus the effect ('reclaim unused space'), so an agent knows exactly what it does. It gives no hint of how this differs from sibling maintenance tools like ctx_purge_session, ctx_purge_expired, or ctx_rebuild_index.

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 precondition (e.g., after large deletions), and no mention of the sibling purge/rebuild tools that an agent might pick instead. The 'reclaim unused space' phrasing implies a maintenance scenario but leaves the choice entirely to inference.

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