Skip to main content
Glama
Sign In
MCP Zephyr

MCP Zephyr

by donyfs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

create_bdd_test_script

Generate BDD test scripts in Gherkin format for Zephyr Scale Cloud, validating steps and structuring scenarios with Given/When/Then syntax.

Instructions

Create a BDD test script using Gherkin format with helper validation

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>"
    },
    "name": "create_bdd_test_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
testCaseKeyYesTest case key (format: [A-Z]+-T[0-9]+)
featureNoFeature description for the BDD script
scenarioNoScenario description for the BDD script
stepsNoArray of Gherkin steps (must start with Given/When/Then/And/But)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 but only states what the tool creates, not how it behaves. It doesn't disclose whether this is a write operation, what permissions might be needed, what happens if validation fails, or what the output looks like. 'Helper validation' is mentioned but not explained.

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 a single, efficient sentence that states the core purpose without unnecessary elaboration. Every word earns its place, and it's appropriately front-loaded with the main action.

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 creation tool with 4 parameters and no annotations or output schema, the description is insufficient. It doesn't explain the creation process, validation behavior, error conditions, or relationship to sibling tools. The mention of 'helper validation' is too vague to be helpful.

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 description coverage is 100%, so the schema already documents all 4 parameters thoroughly. The description adds no additional parameter information beyond what's in the schema, meeting the baseline expectation when schema coverage is complete.

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 a BDD test script') and specifies the format ('using Gherkin format with helper validation'), which distinguishes it from generic test script creation tools. However, it doesn't explicitly differentiate from sibling 'create_test_script' beyond mentioning the BDD/Gherkin aspect.

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_test_case'. The description mentions the format but doesn't explain the specific use cases for BDD test scripts versus other test artifacts.

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