Skip to main content
Glama
Sign In
PatchWarden

PatchWarden

by jiezeng2004-design
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

check_release_gate

Checks release readiness across five sequential stages, stopping at the first failure. Remote stages query npm and GitHub APIs read-only, reporting not_checked on errors.

Instructions

v1.0.0: Verify release readiness across five sequential stages: local_ready → packed_ready → published_verified → github_release_verified → ci_verified. Remote stages (published/github/ci) query npm registry and GitHub API via node:https read-only GET; network errors return 'not_checked' (not 'failed'). Never claims release complete before published_verified passes. Does not execute shell commands for remote queries.

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>",
      "target_stage": "<target_stage>"
    },
    "name": "check_release_gate"
  }
}

Input Schema

NameRequiredDescriptionDefault
branchNoGit branch for ci_verified (e.g. 'main').
versionNoVersion string for published_verified (e.g. '1.0.0'). Required for published_verified stage.
repo_pathYesRepository path inside workspaceRoot.
github_repoNoGitHub repo in 'owner/repo' form for github_release_verified and ci_verified.
package_nameNonpm package name for published_verified (e.g. 'patchwarden'). Required for published_verified stage.
target_stageYesTarget stage to verify. Stages before target are checked; stages after a failure are 'not_checked'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.0

TDQS

A3.5/5.0
Behavior4/5

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

Without annotations, the description carries full burden. It discloses sequential checking, read-only GET via node:https, network error handling as 'not_checked', no premature success claims, and no shell commands for remote queries. Lacks mention of authorization or side effects.

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?

Concise, front-loaded with version and purpose. Every sentence adds value without redundancy. Well-structured for quick comprehension.

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?

Describes stages and behavior but lacks explanation of return format or output structure. Since no output schema exists, this is a gap. Still covers core logic adequately.

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 covers all 6 parameters with descriptions. The description adds context about stage progression and remote query behavior but repeats some schema info (e.g., version required for published_verified). Baseline 3 due to full schema coverage.

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?

The description clearly states 'Verify release readiness across five sequential stages' and lists them. Though it doesn't explicitly differentiate from sibling tools like release_check or release_verify, the purpose is specific and actionable.

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?

No guidance on when to use this tool vs alternatives. Does not state prerequisites or when not to use it. The description only explains what it does, not context for selection.

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