Skip to main content
Glama
Sign In
PatchWarden

PatchWarden

by jiezeng2004-design
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

release_cleanup

Remove low-risk ignored or untracked release artifacts per project auto_cleanup rules, with dry-run enabled by default and an audit summary after non-dry-run cleanup.

Instructions

v1.3.0: Clean up release artifacts using project-policy auto_cleanup rules. Defaults to dry_run=true. Non-dry-run cleanup only removes low-risk ignored/untracked artifacts under repo_path and writes an audit summary.

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": {
      "repo_path": "<repo_path>"
    },
    "name": "release_cleanup"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNoPreview cleanup by default. Set false to remove eligible artifacts.
patternsNoOptional cleanup patterns. Defaults to project policy auto_cleanup.patterns.
repo_pathYesRepository path inside workspaceRoot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, description discloses defaults, scope (low-risk artifacts under repo_path), and audit summary writing. Does not mention permissions or irreversibility, but is transparent for a cleanup tool.

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?

Two sentences, compact and informative. Version prefix is minor overhead but not detrimental. Good structure for quick parsing.

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?

No output schema; description mentions audit summary but not its content. Lacks explicit return value documentation. Adequate for the tool complexity but could be more complete.

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?

Adds value beyond schema: dry_run default true, patterns default to project policy, repo_path context inside workspaceRoot. Schema coverage is 100%, so description enhances understanding.

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 'Clean up release artifacts' using specific rules, with a specific verb and resource. It distinguishes from siblings like release_check, release_prepare, release_verify.

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?

Provides context on default dry_run behavior and scope of non-dry-run removal. Lacks explicit when-not-to-use or alternatives but is clear for typical 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