Skip to main content
Glama

Get Quarantine

get_quarantine
Read-only

Retrieve a test quarantine's reason, assignee, end date, scope, state, change history, and 90-day covered runs to understand why a test was kept from failing.

Instructions

Read one quarantine: reason, assignee, end date, what it covers, its state, and its full history of changes (events). Also returns coveredRuns from the last 90 days (a total plus the 10 latest) — runs a quarantine of this test kept from failing.

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": "get_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 this is a non-destructive, closed-world read, so the bar is lower; the description still adds real value by disclosing the return shape (state plus full event history) and a non-obvious scope limit — coveredRuns covers only the last 90 days and returns a total plus the 10 latest. It does not mention pagination or limits on the events list.

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 action and resource, then the returned fields; the coveredRuns clause is appended with an em dash and earns its place by explaining an otherwise confusing field. It is dense but contains no filler sentences.

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?

With only two parameters and no output schema, the description carries the return-value burden and largely discharges it by listing the fields and explaining the truncated coveredRuns. Minor gaps remain around event ordering/volume and error behavior for an unknown id.

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 100%, with both projectId and quarantine_id documented, including the hint that the id matches list_test_controls output. The description adds no additional parameter meaning beyond the schema, so baseline 3 applies.

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?

Opens with a specific verb and resource ('Read one quarantine') and enumerates the returned fields (reason, assignee, end date, coverage, state, change history), so it is unmistakably a single-record read rather than a write or list operation. It does not name a sibling to contrast with, so it stops short of full differentiation.

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?

Usage is only implied: 'read one quarantine' suggests fetching a single known record, and the schema notes the id comes from list_test_controls. There is no explicit statement of when to prefer this over update_quarantine, release_quarantine, or quarantine_tests.

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