Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Zephyr: Get Test Case Steps

zephyr_get_test_case_steps
Read-onlyIdempotent

Retrieve details of test case steps in Zephyr by providing the test case key and optional pagination parameters.

Instructions

Get details of test case steps in Zephyr

Toolset: Test Cases

Examples:

  1. Get the first 10 test case steps for test case with key 'SA-T1'

{
  "testCaseKey": "SA-T1",
  "maxResults": 10,
  "startAt": 0
}

Expected Output: The first 10 test case steps with their details

  1. Get any test case step for test case with key 'SA-T1'

{
  "testCaseKey": "SA-T1",
  "maxResults": 1
}

Expected Output: One test case step with its details

  1. Get five test case steps starting from the 7th test case step of the list for test case with key 'SA-T1'

{
  "testCaseKey": "SA-T1",
  "maxResults": 5,
  "startAt": 6
}

Expected Output: The 7th to the 11th test case steps with their details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startAtNoZero-indexed starting position. Should be a multiple of maxResults.
maxResultsNoSpecifies the maximum number of results to return in a single call. The default value is 10, and the maximum value that can be requested is 1000. Note that the server may enforce a lower limit than requested, depending on resource availability or other internal constraints. If this happens, the result set may be truncated. Always check the maxResults value in the response to confirm how many results were actually returned.
testCaseKeyYesThe key of the test case. Test case keys are of the format [A-Z]+-T[0-9]+

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nextNoURL to the next page of results, or null if there are no more results.
totalNoIndicates the total number of items available across all pages.
isLastNoIndicates if this is the last page of results.
valuesNoThe list of test steps
startAtYesIndicates the index of the first item returned in the page of results.
maxResultsYesIndicates the maximum number of results in this response. Note that the server may enforce a lower limit than requested, depending on resource availability or other internal constraints.
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the description need not repeat that. It adds value by demonstrating pagination behavior with examples (startAt, maxResults). No contradictions with annotations.

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 concise, with a brief header and three well-structured JSON examples. Each example serves a clear purpose, though the JSON blocks add verbosity. Overall, no redundant sentences.

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 an output schema exists (not shown but indicated), the description does not need to detail return values. It fully covers pagination parameters and usage patterns. Minor gap: no explanation of what a 'test case step' comprises, but this is likely domain knowledge.

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 coverage is 100% with descriptions for all three parameters. The description enhances understanding by providing three concrete examples that illustrate the use of startAt and maxResults together, showing pagination patterns.

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 details of test case steps in Zephyr', which specifies the action (get) and resource (test case steps). Among siblings like zephyr_get_test_case and zephyr_get_test_cycle, it uniquely identifies its function.

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?

The description includes a 'Toolset: Test Cases' header and three examples showing pagination, but it does not explicitly state when to use this tool versus alternatives (e.g., zephyr_get_test_execution_steps or qmetry_fetch_test_case_steps). Usage is implied through examples.

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