Skip to main content
Glama

Release Quarantine

release_quarantine
Destructive

End a test quarantine so its failures fail the build again, moving it to Released with you as releaser while preserving its history.

Instructions

Call this only when the user asks for it. End a quarantine now: the test's failures fail the build again. The quarantine moves to Released with you as the releaser and its history is kept.

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": {
      "projectId": "<projectId>",
      "quarantine_id": "<quarantine_id>"
    },
    "name": "release_quarantine"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesProject ID (e.g. project_<id>)
quarantine_idYesQuarantine id, as list_test_controls returns it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description adds what the destruction actually does — the quarantine transitions to 'Released', the caller is recorded as releaser, and history is preserved. That last detail materially softens the destructive framing. It stops short of saying whether the release can be undone or re-quarantined.

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?

Three short sentences with zero filler, and the gating condition is front-loaded before the effect. Minor redundancy between 'End a quarantine now' and the state-transition sentence, but it reads cleanly.

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?

For a two-parameter mutation with annotations and no output schema, the description covers the trigger condition, the state transition, the audit trail, and the build-impact consequence. Only reversibility/irreversibility is left unstated.

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% and the schema clarifies quarantine_id is 'as list_test_controls returns it', so the description need not document parameters. The description adds no additional meaning beyond the schema, which is the expected baseline here.

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 names a specific verb+resource ('End a quarantine') and states the concrete consequence ('the test's failures fail the build again'), which tells an agent exactly what state change occurs. It does not explicitly distinguish itself from update_quarantine or quarantine_tests, leaving the agent to infer the pairing from names.

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

Usage Guidelines3/5

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

'Call this only when the user asks for it' sets an explicit permission gate, which is real usage guidance. However, it gives no guidance on prerequisites such as inspecting the quarantine first via get_quarantine, or on when update_quarantine would be the better choice, so the alternative-selection guidance is only implied.

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