Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Zephyr: Get Test Script

zephyr_get_test_script
Read-onlyIdempotent

Retrieves the test script (plain text or BDD) for a specified test case in Zephyr, enabling review and analysis of test instructions.

Instructions

Get the Test Script (Plain Text or BDD) for a given Test Case in Zephyr

Toolset: Test Cases

Parameters:

  • testCaseKey (string) required: The key of the test case. Test case keys are of the format [A-Z]+-T[0-9]+

Examples:

  1. Get the test script for test case with key 'SA-T1'

{
  "testCaseKey": "SA-T1"
}

Expected Output: The test script with its type (plain or bdd), text content, and id

  1. Retrieve the BDD test script content for test case with key 'MM2-T15'

{
  "testCaseKey": "MM2-T15"
}

Expected Output: The test script with its type (plain or bdd), text content, and id

  1. Get the test script for test case with key 'QA-T100' to review the test instructions

{
  "testCaseKey": "QA-T100"
}

Expected Output: The test script with its type (plain or bdd), text content, and id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
testCaseKeyYesThe key of the test case. Test case keys are of the format [A-Z]+-T[0-9]+

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe ID of the entity
textYes
typeYesTest scripts can be written in plain text or BDD format. The BDD type supports remote execution on a build system via API plugin. Supported Keywords for BDD: Given, When, Then, And, But. For more information about BDD and Gherkin syntax, see: https://support.smartbear.com/zephyr/docs/en/test-cases/gherkin-behavior-driven-development--bdd-.html For Plain Text scripts, we support HTML fragments. To create a step-by-step test script, you should use the POST /testcases/{testCaseKey}/teststeps endpoint.
Behavior2/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description does not add behavioral context beyond the schema and annotations, such as error handling for missing test cases or rate limits.

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 well-structured with a title, toolset, parameter list, and three examples. Every section adds value, and the content is concise without redundancy.

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

Completeness4/5

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

Given the presence of an output schema, the description adequately covers the tool's purpose and parameter. It could be improved by mentioning what happens if the test case does not exist or has no script.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% coverage with pattern and description. The description reinforces the format and provides multiple examples with expected outputs, adding practical understanding beyond the schema.

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 'Get the Test Script (Plain Text or BDD) for a given Test Case in Zephyr', specifying the verb, resource, and scope. It distinguishes from sibling tools like zephyr_create_test_script or zephyr_get_test_case.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool vs alternatives. The purpose is clear from the name and description, but there is no mention of when not to use or which alternative to choose.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SmartBear/smartbear-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server