MCP Zephyr

list_projects

Retrieve all Jira projects integrated with Zephyr Scale Cloud for test management, with pagination controls to manage result sets.

Instructions

List all Zephyr-integrated Jira projects

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_projects"
  }
}

Input Schema

Name	Required	Description	Default
`maxResults`	No	Maximum number of results to return (default: 50, max: 1000)
`startAt`	No	Starting position for pagination (default: 0)

Schema Changelog

Changes observed during successful MCP inspections.

First observedDec 30, 2025

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the basic action without mentioning pagination behavior (implied by parameters but not described), authentication needs, rate limits, or what 'Zephyr-integrated' specifically entails, leaving significant gaps for a listing operation.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the returned project list includes (e.g., fields, structure), how pagination works in practice, or any error conditions, which are important for a listing tool with pagination parameters.

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?

The input schema has 100% description coverage, thoroughly documenting both parameters with defaults and constraints. The description adds no parameter-specific information beyond what's in the schema, so it meets the baseline score of 3 without compensating value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('List') and resource ('all Zephyr-integrated Jira projects'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_project' (which likely retrieves a single project) or 'list_folders' (which lists a different resource type), missing full sibling distinction.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose 'list_projects' over 'get_project' for single-project retrieval or how it relates to other listing tools like 'list_folders' or 'list_test_cases', leaving usage context unclear.

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

Deploy Server