Skip to main content
Glama

Set Test Critical

set_test_critical
Destructive

Mark or unmark a Playwright test as critical so a critical test that passes only on retry fails the build; unmarking relaxes that rule. Owners and admins only.

Instructions

Call this only when the user asks for it. Mark (critical: true) or unmark (critical: false) a test as critical. A critical test that passes only on retry fails the build; unmarking relaxes that. Owners and admins only. A quarantined test cannot be marked critical, and a project has at most 50 critical tests.

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_id": "<testcase_id>",
      "critical": "<critical>"
    },
    "name": "set_test_critical"
  }
}

Input Schema

NameRequiredDescriptionDefault
criticalYes
projectIdYesProject ID (e.g. project_<id>)
testcase_idYesPlaywright pw_test_id of the test

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the mutation itself is disclosed. The description adds substantial context beyond that: permission level ('Owners and admins only'), a business consequence ('a critical test that passes only on retry fails the build'), and two hard constraints. It stops short of describing the return value or any partial-failure behavior, which keeps it at 4 rather than 5.

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 usage gate, then the action, then the effect, then the constraints. No sentence is redundant; each carries a distinct constraint or consequence.

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 three-parameter mutation tool with no output schema, the description covers permissions, preconditions, quotas, and consequences, which is what an agent needs before calling. The remaining gap is what a successful call returns or how quota exhaustion surfaces, which is not stated anywhere else.

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 67%: projectId and testcase_id are documented in the schema, but the 'critical' boolean is not. The description compensates by defining true as mark and false as unmark, which is the single most important semantic the schema omits. Baseline 3 applies given mostly-covered schema plus one useful clarification, but no format or ID-syntax detail is added beyond what the schema already provides.

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?

The description states a specific verb and resource: 'Mark (critical: true) or unmark (critical: false) a test as critical.' It also spells out the effect of each direction, so an agent can distinguish this from sibling tools like assign_test or watch_test without inspecting any schema.

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

Usage Guidelines5/5

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

It opens with an explicit usage gate ('Call this only when the user asks for it'), which tells the agent not to act proactively. It also supplies conditions that block use (quarantined tests cannot be marked critical) and a scaling limit (at most 50 critical tests per project).

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