Skip to main content
Glama
Sign In
research-hub

research-hub

by WenyuChiou
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

tidy_vault

Perform vault health check with automatic fixes, deduplication rebuild, and cleanup preview. Logs each step and returns total duration.

Instructions

One-shot vault maintenance: doctor autofix + dedup rebuild + bases refresh + cleanup preview.

Each sub-step is non-fatal — failures logged but don't abort the others.

Use when: user says "tidy", "maintenance", "vault health check".

Returns {ok, steps, total_duration_sec, cleanup_preview_bytes}.

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

Input Schema

NameRequiredDescriptionDefault
apply_cleanupNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

Discloses that each sub-step is non-fatal and failures are logged without aborting. However, it does not clarify whether the tool is read-only or modifies the vault by default, nor does it explain the effect of the 'apply_cleanup' parameter on the behavior beyond the preview.

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?

Three concise sentences, front-loaded with the core action, followed by key behavioral notes and usage triggers. Every sentence adds value without redundancy.

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 purpose, behavior, when to use, and return format adequately. Lacks prerequisites or side effects, but given the output schema exists to detail return values, the description is reasonably complete for a multi-step maintenance tool.

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?

With 0% schema coverage, the description adds some meaning by mentioning 'cleanup preview' in the return, but it does not explain how the 'apply_cleanup' parameter affects the tool's behavior. The parameter's role (apply vs preview) is only implied.

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's purpose as 'one-shot vault maintenance' and lists specific sub-steps: doctor autofix, dedup rebuild, bases refresh, and cleanup preview. This distinguishes it from sibling tools like 'run_doctor' or 'cleanup_garbage', which handle individual steps.

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?

Explicitly states when to use: when user says 'tidy', 'maintenance', or 'vault health check'. Does not explicitly list when not to use or alternative tools for single steps, but the context implied by listing sub-steps provides adequate guidance.

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