Skip to main content
Glama

Watch Test

watch_test

Toggle personal watching for a Playwright test so it appears in list_test_controls with the "watched" view.

Instructions

Watch (watching: true) or stop watching (watching: false) a test for yourself. Watched tests are listed by list_test_controls with view "watched".

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

Input Schema

NameRequiredDescriptionDefault
watchingYes
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 cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the description only needs to add context — and it does: the effect is scoped to the calling user ('for yourself') and is reversible by toggling the boolean back. It does not describe idempotency or whether the watch survives across sessions/workspaces, which is the remaining gap.

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?

Two short sentences with no filler: the action and its two modes come first, then the verification pointer. Every clause carries information, and nothing is buried.

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-required-parameter toggle with no output schema, the description supplies the mode semantics, the per-user scope, and the follow-up tool for confirming the new state. The only omission is any indication of the response payload or error behavior (e.g., unknown testcase_id), which is minor given there is no output schema to lean on.

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 67%: projectId and testcase_id are documented in the schema, but `watching` is a bare boolean with no schema description. The description compensates exactly where the schema is silent, defining true as watch and false as stop watching. That is real added meaning beyond the structured fields.

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 names a specific verb pair (watch / stop watching) and the resource (a test), and immediately disambiguates the two modes via the `watching` boolean. It also adds the crucial scope qualifier 'for yourself', which distinguishes this per-user subscription action from the listing tools like list_test_controls.

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 explicit call-time guidance for both branches of the only meaningful parameter (true to watch, false to stop watching) and points the agent at list_test_controls with view "watched" to verify the result. It does not state any when-not conditions or permissions prerequisites, but the guidance is clear enough that an agent would not misfire.

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