qtm4j-mcp-server

add_test_case_steps

Add step details, expected results, and test data to test case versions using structured step arrays.

Instructions

Create test steps on a test case version (POST …/teststeps). steps[].stepDetails is required.

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": {
      "testCaseId": "<testCaseId>",
      "steps": "<steps>"
    },
    "name": "add_test_case_steps"
  }
}

Input Schema

Name	Required	Description
`projectId`	No	QMetry project ID (default: none)
`testCaseId`	Yes	Internal test case id (or key if API accepts)
`versionNo`	No	Test case version number
`steps`	Yes	Steps to create
`aiGenerated`	No	If true, sends aiGenerated=true query flag

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jun 11, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only notes that 'stepDetails' is required but omits critical traits such as whether steps are appended or replaced, side effects, authorization needs, or validation behavior.

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?

The description is a single, front-loaded sentence that efficiently conveys the core action and a key requirement. It is concise and free of extraneous information, though it may be too terse for full understanding.

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

Completeness2/5

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

Given the complexity (5 parameters, no output schema), the description is not complete. It lacks information on return values, error conditions, idempotency, and whether steps are appended or replaced. The tool modifies data but provides no behavioral context beyond the basic action.

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%, so baseline is 3. The description adds minimal value beyond the schema: it reiterates that 'steps[].stepDetails is required', which is already in the schema. No explanation of parameters like aiGenerated, versionNo, or projectId is provided beyond their schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Create test steps') and the resource ('on a test case version'), using a specific verb and noun. It distinguishes from siblings like 'update_test_case_step' and 'get_test_case_steps' by focusing on creation.

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?

The description implies usage for adding steps to a test case version but provides no explicit when-to-use or when-not-to-use guidance. No alternatives or exclusions are mentioned, leaving the context of use inferred.

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