Zephyr Scale MCP Server

delete_test_case

Delete a specific test case in Zephyr Scale Data Center using its key (e.g., PROJ-T123).

Instructions

Delete a specific test case (Data Center only — not supported on Cloud v2)

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": {
      "test_case_key": "<test_case_key>"
    },
    "name": "delete_test_case"
  }
}

Input Schema

Name	Required	Description	Default
`test_case_key`	Yes	Test case key to delete (e.g., PROJ-T123)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Jul 13, 2026

TDQS

A3.6/5.0

Behavior2/5

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states the platform limitation but omits important details for a destructive operation, such as irreversibility, permission requirements, or cascading effects on related data.

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 sentence that conveys essential information efficiently. It is concise, but slightly more structure (e.g., separating the platform note) could improve scannability.

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

Completeness3/5

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

For a simple tool with 1 parameter and no output schema, the description covers the core action and platform limitation. However, it lacks behavioral details (e.g., whether deletion is permanent) that would make it fully informative for agent decision-making.

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 an example format ('e.g., PROJ-T123') which provides clarity beyond the schema's description, but does not elaborate on validation constraints or error conditions.

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 ('Delete a specific test case') and the specific resource, and importantly distinguishes the platform limitation ('Data Center only — not supported on Cloud v2'), which differentiates it from sibling tools that may have different platform support.

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

Usage Guidelines4/5

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

The description explicitly provides a critical usage guideline: it is only applicable for Data Center, not Cloud v2. However, it does not mention any alternatives for Cloud users or when-not-to-use criteria beyond that.

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

Deploy Server