testit-mcp-server

set_test_plan_state

Idempotent

Start, pause, or complete a test plan by ID, updating its status to InProgress, Paused, or Completed for clear test management tracking.

Instructions

Change test plan status: start (-> InProgress), pause (-> Paused), complete (-> Completed).

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Test plan UUID.
`action`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 14, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The annotations already declare that this is a non-read-only, idempotent, non-destructive, open-world mutation, so the description does not need to restate safety basics. It adds useful value by mapping each action to the resulting status, which is behavior beyond the annotations. It does not explain transition rules, permissions, or side effects on related test runs, so a 3 is appropriate.

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?

The definition is a single compact sentence with no wasted wording. The core verb and the three action mappings are front-loaded and immediately scannable.

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 simple two-parameter lifecycle tool with no output schema, the description provides enough information to select and invoke it correctly. It could be stronger if it mentioned transition preconditions or how it relates to update_test_plan, but those are secondary for this complexity level.

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 50%: id is documented, while action has an enum but no schema description. The description compensates well for that gap by explaining what each action value causes: start leads to InProgress, pause to Paused, and complete to Completed. This adds meaning beyond the bare enum, though it does not describe invalid or no-op transitions.

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 states a specific verb and resource: 'Change test plan status.' It also enumerates the three supported actions and their resulting statuses, making the operation unambiguous. It does not explicitly distinguish itself from nearby tools such as update_test_plan or complete_test_run, which keeps it from a 5.

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 by the action-to-status mapping, so an agent can infer that this tool is for lifecycle transitions. However, it gives no explicit guidance on when to choose this over update_test_plan, nor any when-not conditions or transition prerequisites. This is adequate but leaves routing to inference.

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

Deploy Server