Skip to main content
Glama

Quarantine Tests

quarantine_tests
Destructive

Quarantine up to 100 tests until a set date so their failures no longer break the build while tests still run and report; set a reason, optional error scope, assignee, or dry-run preview.

Instructions

Call this only when the user asks for it. Quarantine 1 to 100 tests: until the end date, their failures stop failing the build (they still run and are reported). reason is required and becomes the quarantine note. ends_in_days defaults to the project's default length. assignee defaults to the test's assignee for one test, else to you; the assignee also starts watching the test and is notified when it changes state. only_this_error (one test only) takes an error line and covers only failures with that error; other failures still fail the build. Pass the error of the test's final attempt, the one the build is judged on. dry_run: true creates nothing and reports what would be quarantined, what would be skipped and why, and the quarantine limit — use it before a large quarantine. It does not check only_this_error or that the assignee is a project member; the real call does. Several tests are all-or-nothing against the limit; already quarantined tests are skipped. A quarantine cannot be deleted, only released.

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>",
      "testcase_ids": "<testcase_ids>",
      "reason": "<reason>"
    },
    "name": "quarantine_tests"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesWhy these tests are quarantined
dry_runNo
assigneeNo"me", a user id or a teammate's email
projectIdYesProject ID (e.g. project_<id>)
ends_in_daysNo
testcase_idsYesPlaywright pw_test_ids, as list_testcase returns them
only_this_errorNoThe error line to cover, from the test's final attempt; one test only

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.3
    • changedInput schema / properties / only_this_error / description
      Previous value: -"The error line to cover; one test only"New value: +"The error line to cover, from the test's final attempt; one test only"
  2. Addedv2.2.0

TDQS

A4.2/5.0
Behavior3/5

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

Rich disclosure beyond the annotations: assignee side effects (starts watching, notified on state change), all-or-nothing behavior against the limit, skipping of already-quarantined tests, and the fact that dry_run does not validate only_this_error or project membership while the real call does. It also flags irreversibility ('cannot be deleted, only released'), which is consistent with destructiveHint=true rather than contradicting it.

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 usage gating and the purpose sentence, then parameter semantics, then dry_run and limit edge cases; no sentence is filler. Density is high and several clauses are semicolon-chained, which costs some scannability but not correctness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive 7-parameter mutation with no output schema, the definition covers the effect, defaults, irreversibility, limit behavior, and what dry_run reports. An agent has everything needed to call it correctly, including when to dry-run first.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds real meaning over a 71%-covered schema: reason becomes the quarantine note, ends_in_days falls back to the project default, assignee defaults contextually (test's assignee for one test, else the caller) and carries watching/notification semantics, and only_this_error is constrained to a single test and to the final attempt's error line. testcase_ids format is left entirely to 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?

States a specific verb and resource with explicit scope: 'Quarantine 1 to 100 tests: until the end date, their failures stop failing the build (they still run and are reported).' The batch bound and the effect on build status make it unmistakably distinct from get/update/release quarantine operations without needing to name them.

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?

Gives an explicit gating condition ('Call this only when the user asks for it') plus a workflow rule ('use it before a large quarantine') and skip behavior for already-quarantined tests. It stops short of naming release_quarantine or update_quarantine as the alternatives for other quarantine operations, leaving that inference to the agent.

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