Skip to main content
Glama

Update Quarantine

update_quarantine
Destructive

Change an active quarantine by updating its end date, assignee, note, or linked ticket. Only the fields you pass are modified; all other quarantine details stay unchanged.

Instructions

Call this only when the user asks for it. Change an active quarantine: its end date (ends_in_days, counted from today), assignee, note, or linked ticket (issue_key, issue_url). Only the fields you pass change; the others stay as they are, even if someone edits them at the same time. A quarantine always has an assignee.

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": "update_quarantine"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoReplaces the note; "" clears it
assigneeNo"me", a user id or a teammate's email
issue_keyNoTicket key, e.g. "TD-123"
issue_urlNohttp(s) link to the ticket
projectIdYesProject ID (e.g. project_<id>)
ends_in_daysNo
quarantine_idYesQuarantine id, as list_test_controls returns it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.3
    • changedInput schema / properties / issue_key / maxLength
      Previous value: -128New value: +64
  2. Addedv2.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and readOnlyHint=false; the description adds genuinely new behavior: per-field partial updates, last-write-wins semantics when others edit concurrently, and the invariant that an assignee always exists. It never explains what is destructive (e.g. that an empty note clears it), which the schema hints at but the description does not surface.

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?

Four tight sentences with no repetition; the partial-update rule and the assignee invariant each earn their place. The gating instruction leads, which is slightly ahead of the purpose statement that would better front-load the description.

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 7-parameter mutation with no output schema, the description covers the field scope, update semantics, and the assignee constraint, which is most of what an agent needs. It leaves open what a successful call returns and whether the call fails on a non-active quarantine.

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 86%, so the baseline is 3, and the description earns above that: it explains that ends_in_days counts from today (the schema leaves that parameter undocumented) and ties issue_key/issue_url to a linked ticket. It does not clarify whether ends_in_days can shorten an existing quarantine or only extend it.

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?

"Change an active quarantine" gives a specific verb and resource, and the enumeration of mutable fields (end date, assignee, note, linked ticket) makes the scope unambiguous. It does not name a sibling such as release_quarantine to draw the boundary, 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 Guidelines4/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" is an explicit, unusually strong gating condition, and "active quarantine" implies the objects it applies to. What is missing is any routing statement toward or away from adjacent mutators like release_quarantine.

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