Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Zephyr: Get Projects

zephyr_get_projects
Read-onlyIdempotent

Retrieve Zephyr project details with paginated results. Use maxResults and startAt parameters to fetch specific project subsets.

Instructions

Get details of projects in Zephyr

Toolset: Projects

Parameters:

  • 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 10 projects

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

Expected Output: The first 10 projects with their details

  1. Get any project

{
  "maxResults": 1
}

Expected Output: One project with its details

  1. Get five projects starting from the 7th project of the list

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

Expected Output: The 7th to the 11th projects 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.

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 declare the tool as read-only, idempotent, and non-destructive. The description adds behavioral details about pagination: the server may enforce a lower limit for maxResults, and results may be truncated. It advises checking the response for actual maxResults.

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 well-structured with a brief intro, parameter details, and numbered examples. It is somewhat lengthy due to examples, but the structure is clear and front-loaded with the purpose.

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

Completeness5/5

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

Given the tool's simplicity (listing with pagination) and the presence of an output schema, the description adequately addresses the main complexity: pagination behavior and response truncation. No gaps for this use case.

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 coverage is 100%, so the schema already describes both parameters. The description repeats parameter details but adds examples showing valid parameter combinations and expected outputs, which aids understanding without adding new semantic meaning.

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 projects in Zephyr', specifying the verb 'Get', the resource 'projects', and the domain 'Zephyr'. It distinguishes from related tools like 'zephyr_get_project' (which retrieves a single project) by implying a list operation.

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 versus alternatives like 'zephyr_get_project' or other project-listing tools. However, examples illustrate pagination usage patterns, providing implicit context.

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