Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Zephyr: Get Environments

zephyr_get_environments
Read-onlyIdempotent

Retrieve Zephyr test environments, filtered by Jira project key, with pagination to control result size and starting position.

Instructions

Get environments in Zephyr

Toolset: Environment

Parameters:

  • projectKey (string): Jira project key filter

  • maxResults (number): Specifies 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. (default: 10)

  • startAt (number): Zero-indexed starting position. Should be a multiple of maxResults. (default: 0)

Examples:

  1. Get the first 20 Environments

{
  "maxResults": 20,
  "startAt": 0
}

Expected Output: The first 20 Environments with their details from different projects

  1. Get the first 10 Environments from the project with projectKey TEST

{
  "projectKey": "TEST",
  "maxResults": 10,
  "startAt": 0
}

Expected Output: The first 10 Environments with their details from project with projectKey TEST

  1. Get second 10 Environments from the project with projectKey TEST

{
  "projectKey": "TEST",
  "maxResults": 10,
  "startAt": 10
}

Expected Output: The second 10 Environments with their details from project with projectKey TEST

  1. Get Environments starting from the 5th Environment from different projects

{
  "startAt": 5,
  "maxResults": 10
}

Expected Output: Environments starting from the 5th one with their details from different projects

  1. Get 5 Environments starting from the 10th Environment from the project with projectKey PROJ

{
  "startAt": 10,
  "maxResults": 5,
  "projectKey": "PROJ"
}

Expected Output: The five environments starting from the 10th Environment from the project PROJ 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.
projectKeyNoJira project key filter

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.
valuesNo
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.
Install Server

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful behavior beyond that: the server may cap maxResults lower than requested, results may be truncated, and callers should check the response's maxResults value. This is relevant operational context for a paginated read-only tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and the markdown structure is readable, but the Parameters section largely duplicates the input schema verbatim. The five examples are instructive, but several are repetitive, and the internal contradiction in Example 4 makes the extra length less valuable than it could be.

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?

For a simple read-only list tool with an output schema, the description covers the key agent-facing needs: optional project filtering, pagination semantics, defaults, and truncation behavior. It is complete enough to call correctly, though the pagination inconsistency and lack of alternative-tool routing keep it from being fully polished.

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 description does not need to add much. It restates the schema and provides examples, but it introduces an inconsistency: the description says startAt should be a multiple of maxResults, yet Example 4 uses startAt=5 with maxResults=10. It also states a maxResults request ceiling of 1000 while the schema maximum is far larger. These contradictions reduce the value of the added param guidance.

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 opens with 'Get environments in Zephyr', clearly specifying a verb, a resource, and a product domain. The 'Toolset: Environment' label and the tool name itself distinguish it from the many other zephyr_get_* sibling tools.

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 examples make the intended usage fairly clear: list environments, optionally filter by projectKey, and page with startAt/maxResults. However, there is no explicit guidance about when to prefer this tool over an alternative, and no 'when not to use' statement. One example even contradicts the stated pagination rule, which weakens the usage guidance.

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

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