Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Zephyr: Get Environments

zephyr_get_environments
Read-onlyIdempotent

Retrieve environments in Zephyr with optional project key filter and pagination controls for max results and start 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.
Behavior4/5

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

Annotations already indicate read-only and idempotent behavior. The description adds useful pagination details, including server truncation and the recommendation that startAt should be a multiple of 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 front-loaded with the purpose, followed by parameter details and examples. While the examples add length, they are well-structured and aid comprehension. Minor redundancy ('Toolset: Environment') could be trimmed.

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 simple nature of the tool (list environments with optional filters) and the presence of an output schema, the description covers purpose, parameters, pagination behavior, and examples. Missing ordering of results is a minor gap, but overall sufficient.

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%, so baseline is 3. The description adds concrete examples showing parameter combinations and usage, enhancing understanding beyond the schema alone. It also repeats the server truncation note from the schema, which is helpful.

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 starts with 'Get environments in Zephyr', clearly stating the verb and resource. Among sibling tools, this is the only Zephyr-specific environment retrieval tool, distinguishing it from other environment-related tools like contract-testing_get_environment.

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

Usage Guidelines4/5

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

The description provides clear context by specifying 'in Zephyr' and details on filtering by projectKey. However, it does not explicitly mention when to use this tool over alternatives, such as contract-testing environment tools, though the domain is implied.

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