PatchWarden

safe_status

Retrieve minimal task lifecycle status while protecting diffs, logs, file contents, and sensitive paths. Use when only state is needed and content-bearing tools are blocked.

Instructions

Return minimal task lifecycle status without exposing diff, log content, file contents, or sensitive paths. Use this when only task state is needed and content-bearing tools may be blocked by upper-layer security.

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": {
      "task_id": "<task_id>"
    },
    "name": "safe_status"
  }
}

Input Schema

Name	Required	Description	Default
`task_id`	Yes	Task ID to check

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.0Jul 8, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries full burden for behavioral disclosure. It clearly states what the tool does not expose (sensitive content), indicating it is a safe, read-only operation. However, it does not describe error handling or response format, but given the tool's simplicity and safety focus, it is transparent enough.

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, front-loaded with purpose and constraints. Every sentence adds value with zero waste. Exceptionally concise while being informative.

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?

The tool has no output schema, so the description should explain the return value. It mentions 'minimal task lifecycle status' but does not specify what status values look like (e.g., states like pending, completed, failed). For a minimal tool, this is a slight gap, but it aligns with the 'minimal' theme. Could be improved with brief enumeration.

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% (task_id described as 'Task ID to check'). The description adds no further parameter details, so baseline of 3 applies. No additional semantics are provided beyond the schema.

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 explicitly states the verb 'return' and resource 'minimal task lifecycle status', and specifies what is excluded (diff, log, file contents, sensitive paths). This clearly distinguishes it from sibling tools like get_task_status or safe_audit which may expose more content.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Directly advises when to use: 'when only task state is needed and content-bearing tools may be blocked by upper-layer security'. This also implies when not to use (when content is needed), and references alternative tool categories.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server