teardown-observe

Overview Schema Source Related Servers Discussions Admin

release_spec

Release a draft through the approval gate: strict mode needs all findings approved and gaps acknowledged; standard mode blocks unexercised coverage unless accept_gaps explains it.

Instructions

Release a draft through the gate. Strict mode: succeeds only once a person has approved every finding and acknowledged coverage gaps (teardown approve); rewrite prose findings instead of waiting for approval. Standard mode: refused while measured coverage items are neither exercised nor explained, unless accept_gaps gives the reason they ship as unknowns.

Input Schema

Name	Required	Description	Default
`draft_id`	Yes
`accept_gaps`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.2.0Oct 24, 2026

addedInput schema / properties / accept_gaps

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Accept Gaps"
+}

First observedv0.1.0Oct 23, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Without annotations, the description carries the behavioral burden: it discloses strict mode requirements (approval of every finding, acknowledged coverage gaps), the alternative of rewriting prose findings, and standard mode refusal conditions. It does not cover permissions or reversibility, but provides rich gating behavior.

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?

Front-loaded with the core action ('Release a draft through the gate') followed by mode-specific details. Dense but every sentence adds behavioral context; no wasted words.

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?

Given an output schema exists and no annotations are present, the description covers the key gating behaviors and modes. It omits what 'gate' means operationally, but overall provides enough for an agent to call correctly.

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 0%, so the description must compensate. It explains accept_gaps meaningfully ('gives the reason they ship as unknowns'), but does not explain draft_id beyond its self-evident name. Adequate but not fully compensating.

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?

States a specific verb ('Release') and resource ('a draft'), and explains the gating conditions. It distinguishes itself from siblings like approve_observed_output by focusing on releasing after approvals, though it does not explicitly name alternatives.

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?

Explains when the tool succeeds in strict mode and when it is refused in standard mode, and mentions accept_gaps as a condition. It gives clear context for use but does not explicitly compare to siblings or state when to prefer this over review_spec.

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