Skip to main content
Glama

Get Test Controls

get_test_controls
Read-only

Retrieves a Playwright test's controls—assignee, critical/watch status, active quarantine—and last-90-day affected runs to help agents assess test risk and quarantine impact.

Instructions

Read the Test Controls of one test: its assignee, whether it is critical, whether you watch it, and its active quarantine. Also returns affectedRuns from the last 90 days (a total plus the 10 latest): excluded — runs a quarantine kept this test from failing; critical — runs this test failed because it passed only on retry while marked critical. Takes the Playwright test id (testcase_id), as list_testcase returns it.

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>"
    },
    "name": "get_test_controls"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.1/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description goes beyond that by disclosing a real data-window constraint (affectedRuns limited to the last 90 days, a total plus the 10 latest) and defining the 'excluded' and 'critical' categories, which materially shapes how an agent should interpret results.

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?

The returned fields are front-loaded in the first sentence, and the second sentence handles the affectedRuns semantics. It is dense but each clause carries information; the em-dash list of two run categories is slightly compressed but not wasteful.

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?

With no output schema, the description must describe return values, and it does so field by field, including the two aggregate run categories and the 90-day/10-latest limits. Combined with full schema coverage of both parameters and annotations covering the safety profile, nothing an agent needs to call and interpret this tool is missing.

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 schema baseline alone would justify a 3. The description adds genuine meaning by identifying testcase_id as the Playwright test id in the exact form returned by list_testcase, which is more actionable than the schema's terse 'Playwright pw_test_id of the test'.

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?

The description opens with a specific verb and resource ('Read the Test Controls of one test') and then enumerates exactly what is returned: assignee, critical flag, watch status, active quarantine. The scope word 'one' implicitly distinguishes it from the plural sibling list_test_controls, but no sibling is named explicitly, so the differentiation is inferred rather than stated.

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?

It gives a clear precondition for correct invocation: the tool takes the Playwright test id 'as list_testcase returns it', which tells the agent where to obtain the required identifier. There is no explicit statement of when not to use it (e.g. bulk retrieval via list_test_controls), leaving that to inference.

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