Skip to main content
Glama
Sign In
MCP Zephyr

MCP Zephyr

by donyfs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

create_test_case

Create test cases in Zephyr Scale Cloud for Jira projects to manage testing processes with structured objectives, preconditions, and labels.

Instructions

Create a new test case

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": {
      "name": "<name>",
      "projectKey": "<projectKey>"
    },
    "name": "create_test_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the test case
projectKeyYesJira project key where the test case will be created
descriptionNoDescription of the test case
folderIdNoFolder ID where the test case will be created
componentNoComponent ID for the test case
labelsNoLabels for the test case (single string or array of strings)
objectiveNoTest objective
preconditionNoTest precondition
estimatedTimeNoEstimated time in minutes (will be converted to milliseconds)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Create a new test case' implies a write/mutation operation but provides no information about permissions needed, whether creation is reversible, what happens on failure, rate limits, or what the response contains. This is inadequate for a mutation tool with zero annotation coverage.

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 description is extremely concise at just three words. It's front-loaded with the essential action and resource. There's zero wasted language or redundancy. For a tool with comprehensive schema documentation, this brevity is appropriate.

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?

For a mutation tool with 9 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what a test case is in this system, how it differs from test scripts, what happens after creation, or any behavioral aspects. The agent would need to infer too much from just 'Create a new test case'.

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?

The schema description coverage is 100%, so all parameters are documented in the schema itself. The description adds no additional parameter information beyond what's already in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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

Purpose3/5

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

The description 'Create a new test case' clearly states the action (create) and resource (test case), but it's generic and doesn't differentiate from sibling tools like 'create_test_script' or 'create_bdd_test_script'. It lacks specificity about what distinguishes a test case from other test artifacts in this system.

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?

No guidance is provided about when to use this tool versus alternatives like 'create_test_script' or 'create_bdd_test_script'. The description doesn't mention prerequisites, dependencies, or contextual factors that would help an agent decide between this and sibling creation tools.

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

Deploy Server

Other Tools