Skip to main content
Glama

Manage test quarantine

manage_test_quarantine
Destructive

Change a connected repository's flaky-test quarantine. action quarantine quarantines one test (test_key and reason), so its failures stop failing runs. action release ends a quarantine (quarantine_id, optional reason). action settings changes the quarantine's settings; name only the ones to change. Address the repository with exactly one of repository_id, application_id, or owner and repo. Needs pipelines.manage.

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": {
      "action": "<action>"
    },
    "name": "manage_test_quarantine"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoNoRepository name, with owner.
ownerNoRepository owner (organisation or user), with repo, instead of repository_id.
actionYesWhat to do.
reasonNoWhy: required to quarantine, optional on release. At most 500 characters.
enabledNosettings only: turn the quarantine on or off.
providerNoNarrows owner and repo when the same repository is connected on two providers.
test_keyNoquarantine only: the test's 64-character key.
min_samplesNosettings only: how many observed runs a test needs before it is proposed.
quarantine_idNorelease only: the quarantine's id.
repository_idNoThe connected repository's id, from list_pipeline_repositories.
application_idNoAn application whose linked repository to address, instead of repository_id.
min_flaky_rateNosettings only: the flaky rate, 0 to 1, from which a test is proposed.
release_after_passesNosettings only: consecutive passes after which a quarantine is released.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is known; the description adds real context on top: the outcome of quarantine ("its failures stop failing runs"), the permission needed, and the partial-update semantics of settings ("name only the ones to change"). It does not say what happens when quarantining an already-quarantined test, nor how settings defaults behave when fields are omitted.

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?

Four short sentences, front-loaded with the resource and then the three actions in enum order, with addressing and permission last. Every clause carries operational information; nothing is repeated from the schema verbatim.

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 13-parameter destructive tool with no output schema, the description covers action selection, per-action required fields, repository addressing, and authorization, which is most of what an agent needs. Gaps remain around return behavior (no output schema to fall back on) and edge cases such as re-quarantining or the effect of settings on existing quarantines.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds cross-parameter constraints the schema cannot express: which parameters belong to which action and the mutually exclusive repository addressing ("exactly one of repository_id, application_id, or owner and repo"). That is meaningful meaning beyond the individual field descriptions.

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 ("Change a connected repository's flaky-test quarantine") and then enumerates all three actions with their effects, so an agent can tell quarantine from release from settings without opening the schema. It is clearly a mutation tool, not a read or listing tool.

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 explicit per-action routing: quarantine requires test_key and reason, release requires quarantine_id with optional reason, settings takes only the fields to change. It also states the addressing rule (exactly one of repository_id, application_id, or owner+repo) and the pipelines.manage requirement. It stops short of naming any sibling alternative or a when-not-to-use case, which keeps it below a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.