Skip to main content
Glama
Sign In
SuperSkill

SuperSkill

by permanu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

hygiene_report

Read-only

Scans repos for stale build caches, git worktrees, docker, xcode, and agent scratch. Flags entries due for cleanup with reasons and exact remediation commands.

Instructions

Read-only machine-wide space hygiene report across mapped repos: build caches, git worktrees, docker, xcode, and agent scratch. Marks entries that are DUE for cleanup with reasons and exact remediation commands. Reports only — deletes nothing.

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

Input Schema

NameRequiredDescriptionDefault
dueNoOnly report entries that are due for cleanup
sizesNoMeasure on-disk sizes (slower, more accurate)
categoriesNoLimit to these categories (default: all)
workspace_pathNoAbsolute thread workspace directory; must map to this project. Omit only when the server cwd is the thread workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.1
    • addedInput schema / properties / workspace_path
      Added value: +{
+  "description": "Absolute thread workspace directory; must map to this project. Omit only when the server cwd is the thread workspace.",
+  "type": "string"
+}
  2. Addedv0.13.0

TDQS

A4.2/5.0
Behavior4/5

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

readOnlyHint=true already establishes the safety profile, and the description reinforces it with 'Read-only' and 'deletes nothing'. It adds real context beyond the annotation: the report spans mapped repos, flags DUE entries with reasons, and surfaces exact remediation commands. No output schema exists, so this return-shape detail is genuinely valuable.

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 sentences, zero filler, scope and category list front-loaded, and the non-destructive guarantee placed last where it matters most. Every clause earns its place.

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 no output schema, the description carries the return-value burden and does so well: it explains that entries are marked DUE with reasons and remediation commands. Minor gaps remain around cost/pagination behavior (the schema hints 'sizes' is slower) and how repos are discovered, keeping it from a 5.

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 all four parameters are already documented in the schema, and the description largely restates them by naming the category set. It adds only marginal meaning (machine-wide scope, repo mapping requirement) beyond what the schema provides — baseline 3 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?

States a specific verb (report) and resource (machine-wide space hygiene across mapped repos) and enumerates the exact categories covered: build caches, git worktrees, docker, xcode, agent scratch. The closing 'Reports only — deletes nothing' separates it cleanly from destructive siblings like worktree_gc or prune.

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 'Reports only — deletes nothing' framing makes the use case clear (inspect before cleaning) and implicitly contrasts with deletion-oriented siblings. It never names a specific alternative tool (e.g. worktree_gc) or states when *not* to use it, so it stops short of a 5.

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