-
Notifications
You must be signed in to change notification settings - Fork 18
Description
Component: SmartBear Zephyr MCP Server
Affected Tool: zephyr_get_test_case
Severity: High (blocks all tool usage)
Date: January 27, 2026
Summary
The zephyr_get_test_case tool fails with MCP error -32602 due to output schema validation rejecting additional properties returned by the Zephyr Scale API.
Steps to Reproduce
Call zephyr_get_test_case with a valid test case key
Example parameters:
{
"testCaseKey": "SQA-T35013"
}
{ "testCaseKey": "SQA-T35013" }
Actual Result
MCP error -32602: Structured content does not match the tool's output schema:
data/project must NOT have additional properties,
data/project must NOT have additional properties,
data/priority must NOT have additional properties,
data/priority must NOT have additional properties,
data/status must NOT have additional properties,
data/status must NOT have additional properties,
data/folder must NOT have additional properties,
data/folder must NOT have additional properties,
data/folder must be null,
data/folder must match a schema in anyOf,
data/links must NOT have additional properties,
data/links must NOT have additional properties,
data/links must NOT have additional properties
MCP error -32602: Structured content does not match the tool's output schema: data/project must NOT have additional properties, data/project must NOT have additional properties, data/priority must NOT have additional properties, data/priority must NOT have additional properties, data/status must NOT have additional properties, data/status must NOT have additional properties, data/folder must NOT have additional properties, data/folder must NOT have additional properties, data/folder must be null, data/folder must match a schema in anyOf, data/links must NOT have additional properties, data/links must NOT have additional properties, data/links must NOT have additional properties
Expected Result
The tool should return the test case data successfully.
Root Cause Analysis
The MCP tool's output schema appears to have additionalProperties: false set on the following objects:
project
priority
status
folder
links
This causes JSON Schema validation to fail even though the API response is valid.
Solution:
Set additionalProperties: true on the affected object schemas to allow for API evolution
MCP Server: smartbear (Zephyr Scale integration)
Tool: zephyr_get_test_case
Zephyr Scale API: Cloud version
Workaround:
Currently using direct REST API calls to Zephyr Scale, bypassing the MCP tool entirely.