Skip to main content
Glama
Sign In
MCP Zephyr

MCP Zephyr

by donyfs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

create_test_script

Generate or update test scripts for Zephyr Scale Cloud test cases using Gherkin or plain text formats to define testing procedures.

Instructions

Create or update a test script for a test case (removes existing test steps)

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": {
      "testCaseKey": "<testCaseKey>",
      "text": "<text>"
    },
    "name": "create_test_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
testCaseKeyYesTest case key (format: [A-Z]+-T[0-9]+)
textYesTest script content (Gherkin format for bdd type, plain text for plain type)
typeNoScript type (default: bdd)bdd

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that the tool 'removes existing test steps', indicating a destructive mutation, which is a critical behavioral trait. However, it lacks details on permissions, error handling, or response format, leaving gaps in transparency for a mutation tool.

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, efficient sentence that front-loads the core action ('Create or update a test script') and includes a key behavioral note ('removes existing test steps'). It avoids redundancy and is appropriately sized for the tool's complexity, though it could be slightly more structured with usage context.

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?

Given the tool's mutation nature, lack of annotations, and no output schema, the description is moderately complete. It covers the destructive behavior and basic purpose but omits details on permissions, error cases, or return values, which are important for a tool that modifies data without structured output documentation.

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 input schema has 100% description coverage, providing clear details for all parameters (testCaseKey, text, type). The description does not add any additional semantic meaning beyond what the schema already explains, such as clarifying parameter interactions or constraints, so it meets the baseline but does not enhance understanding.

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 clearly states the action ('Create or update a test script') and the target resource ('for a test case'), which is specific and actionable. However, it does not explicitly differentiate from sibling tools like 'create_bdd_test_script' or 'append_test_steps', which reduces clarity in distinguishing when to use this tool versus alternatives.

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 provides no guidance on when to use this tool versus alternatives such as 'create_bdd_test_script' or 'append_test_steps'. It mentions that it 'removes existing test steps', which hints at a destructive behavior, but does not specify scenarios or prerequisites for its use, leaving the agent without clear usage context.

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