Skip to main content
Glama
Sign In
PatchWarden

PatchWarden

by jiezeng2004-design
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

accept_subgoal

Accept a subgoal after all associated tasks are approved through audit, confirming completion for the guarded execution workflow.

Instructions

Accept a subgoal after all associated tasks are accepted by audit_task. Supports both legacy status=accepted and done_by_agent with acceptance_status=accepted.

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": {
      "goal_id": "<goal_id>",
      "subgoal_id": "<subgoal_id>"
    },
    "name": "accept_subgoal"
  }
}

Input Schema

NameRequiredDescriptionDefault
goal_idYesGoal ID.
subgoal_idYesSubgoal ID to accept.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.7
  2. Removedv1.6.6
  3. First observedv1.5.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It reveals support for two acceptance mechanisms (legacy and done_by_agent), but does not disclose side effects, permissions, or return values, leaving some behavioral gaps.

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 that front-load the purpose and condition. Every word earns its place; no redundant or vague phrasing.

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?

For a simple mutation tool with two string params and no output schema, the description covers the core purpose and precondition. However, it lacks details on error conditions or the exact effect, making it adequate but not comprehensive.

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 coverage is 100% with basic descriptions for goal_id and subgoal_id. The description does not add additional semantic meaning for these parameters beyond what the schema provides, thus baseline of 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?

The description clearly states the tool's action ('Accept a subgoal') and specifies the precondition ('after all associated tasks are accepted by audit_task'). It also notes support for two status formats, distinguishing it from siblings like reject_subgoal.

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 description explicitly states when the tool should be used: after audit_task has accepted all associated tasks. This provides clear context, though it does not explicitly list alternatives or when not to use it.

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