testit-mcp-server

set_test_suite_work_items

Idempotent

Replaces a test suite's work items and creates test points for each work item across suite configurations, using the default configuration when none is set.

Instructions

Set the work items of a test suite. REPLACES the current list; test points are created for each work item x suite configuration (the default configuration if none set).

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Test suite UUID.
`workItemIds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 14, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations cover safety (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the bar is lower, yet the description still adds real behavior: the existing list is fully replaced and test points are generated per work item against each suite configuration, defaulting when none is configured. Those side effects are not derivable from the annotations and are the main risk an agent needs to know; only permission/auth requirements and what happens to prior test-point results are unstated.

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 tight sentences with the destructive-ish replacement warning front-loaded ahead of the secondary side-effect detail. Nothing is wasted and nothing essential 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 two-parameter mutation with no output schema, the definition covers purpose, replacement semantics, and generated side effects, which is close to sufficient. It stops short of covering permissions, return value, or the fate of existing test points/results tied to removed work items.

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 50% – id is documented as the suite UUID while workItemIds is bare – so the description partially compensates by explaining that each supplied work item yields test points per configuration. It adds useful cross-product meaning but says nothing about edge cases such as an empty array (presumably clearing the list) or whether work items must already exist.

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 ("Set the work items of a test suite") and immediately clarifies the replacement semantics, which separates it in spirit from list/search_work_items and from suite-configuration tools. It does not name a sibling explicitly, so differentiation relies on the reader's knowledge of the catalog.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the word "Set" plus "REPLACES the current list" tells an agent this is the assignment operation, but there is no explicit guidance on when to choose this over set_test_suite_configurations or set_test_suite, nor any prerequisites such as needed permissions.

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

Deploy Server