Skip to main content
Glama

Assign Test

assign_test
Destructive

Assign a test case to a project member by email or user ID, to yourself with "me", or unassign it with null; the assignee watches the test and gets notified of state changes.

Instructions

Assign a test to a project member by email or user id, to yourself with "me", or unassign it with null. The assignee also starts watching the test and is notified when it changes state. Someone who is not on the project gets "Owner is not a member of this project."

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

Input Schema

NameRequiredDescriptionDefault
assigneeYes"me", a user id, a teammate's email, or null to unassign
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

A3.6/5.0
Behavior3/5

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

Annotations already declare a non-read-only, destructive-capable, closed-world mutation. The description earns credit by disclosing the side effects annotations cannot express — the assignee begins watching the test and is notified on state change — and by quoting the non-member error. It does not describe whether reassignment replaces a prior watcher nor what the tool returns.

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?

Three compact sentences, front-loaded with the core action and the argument modes, then side effects, then the error. Nothing is redundant, though the quoted error string is slightly more than an agent strictly needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter mutation with no output schema, the description covers the arguments, the side effects, and the main failure mode, which is adequate. Missing are the response shape and whether re-assigning replaces or adds a watcher, both of which an agent may need to reason about.

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%, and the schema already documents exactly what the description says about "me", user id, email, and null. The description adds only the non-member error context, so it sits at the baseline rather than exceeding 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?

The description opens with a specific verb and resource ('Assign a test to a project member') and enumerates the three addressing modes (email, user id, "me") plus the null-unassign case. The action is unmistakably distinct from siblings like watch_test or set_test_critical, though no sibling is named explicitly.

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 concrete selection guidance across the assignee argument: email or user id for another member, "me" for self, null to unassign. It also states the failure precondition (assignee must be a project member). It stops short of contrasting with alternatives such as watch_test for pure watching.

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