testit-mcp-server

link_autotest_work_item

Idempotent

Links an autotest to a TestIT work item, marking the test case as automated so automated coverage stays traceable.

Instructions

Link an autotest to a work item; the work item becomes automated.

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>",
      "workItemId": "<workItemId>"
    },
    "name": "link_autotest_work_item"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Autotest UUID.
`workItemId`	Yes	Work item (test case) UUID.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 14, 2026

TDQS

A3.6/5.0

Behavior4/5

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

The annotations already declare that this is a non-destructive, idempotent, open-world write. The description then adds a real behavioral consequence absent from those annotations: linking changes the work item's state so that it 'becomes automated'. It doesn't say whether re-linking is a no-op or how to undo the change, but the side effect disclosure is the important part.

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?

One sentence, two clauses, front-loaded with the action and ending on the consequence. Nothing is redundant, and no wording could be removed without losing either the action or the state change.

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?

This is a simple two-parameter tool with full schema coverage, no output schema, and annotations that already cover idempotency and safety. The one meaningful gap is the absence of undo or duplicate-link behavior, which matters for a state-changing link operation but is a minor omission here.

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%, so 'id' as an autotest UUID and 'workItemId' as a test-case UUID are already fully documented. The description adds no extra parameter meaning such as format, ordering, or whether ids must come from the same project, so the baseline score of 3 applies.

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 uses a specific verb and names both resources: 'Link an autotest to a work item'. This clearly separates it from the sibling 'unlink_autotest_work_item' by verb alone. It stops short of a 5 because it doesn't explicitly contrast with that sibling or with related tools such as 'list_work_item_autotests'.

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?

The description gives no explicit when-to-use guidance, no prerequisites, and no mention of the natural alternative ('unlink_autotest_work_item') or of tools that already list these links. The intended use is only weakly inferable from the verb 'link'.

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

Deploy Server