testit-mcp-server

unassign_test_points_tester

DestructiveIdempotent

Removes the tester from selected test points in a TestIT test plan and returns the affected test point IDs, helping correct assignments when testers should no longer be responsible.

Instructions

Remove the tester from the given test points of a test plan. Returns the affected point ids.

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": {
      "id": "<id>",
      "testPointIds": "<testPointIds>"
    },
    "name": "unassign_test_points_tester"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Test plan UUID.
`testPointIds`	Yes	Test point UUIDs (see list_test_suite_test_points / search_test_points). Must not be empty.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 14, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true and readOnlyHint=false, so the risk profile is known. The description adds the return contract ('Returns the affected point ids'), which matters because no output schema exists, but says nothing about permission requirements or what happens when a tester is not currently assigned (partial/no-op behavior).

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 sentences, action first, return value second. Nothing is wasted and the key operation is front-loaded.

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 two-parameter mutation tool with full schema coverage and rich annotations, the description covers the action, the scope, and the return value. The only meaningful gap is behavior when some or all testers were never assigned, which the idempotent annotation only partly addresses.

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 description coverage is 100%, with both 'id' (test plan UUID) and 'testPointIds' (non-empty array of test point UUIDs) documented in the schema, including pointers to list_test_suite_test_points and search_test_points. The description only restates that the points belong to a test plan, adding no syntax or edge-case detail beyond the schema.

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?

States a specific verb and resource: 'Remove the tester from the given test points of a test plan.' This is unambiguously the inverse of assign_test_points_tester, so an agent can distinguish direction of the operation, though the description never names that sibling explicitly.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no mention of assign_test_points_tester as the counterpart operation. The inverse relationship is only inferable from the tool name, not from the description text.

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

Deploy Server