Skip to main content
Glama

get_project_test_sets

Retrieve all test sets for a specific Jira project to manage testing resources and organize test cases for execution.

Instructions

Get all test sets for a specific project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectKeyYesThe Jira project key (e.g., "PROJ")
maxResultsNoMaximum number of results to return

Implementation Reference

  • src/index.ts:446-464 (registration)
    Registration of the 'get_project_test_sets' tool in the tools array, including name, description, and input schema used for listing tools.
    {
      name: 'get_project_test_sets',
      description: 'Get all test sets for a specific project',
      inputSchema: {
        type: 'object',
        properties: {
          projectKey: {
            type: 'string',
            description: 'The Jira project key (e.g., "PROJ")',
          },
          maxResults: {
            type: 'number',
            description: 'Maximum number of results to return',
            default: 50,
          },
        },
        required: ['projectKey'],
      },
    },
  • MCP tool execution handler: extracts projectKey and optional maxResults from arguments, calls xrayClient.getTestSetsByProject, serializes result as JSON text response.
    case 'get_project_test_sets': {
      const result = await xrayClient.getTestSetsByProject(
        args.projectKey as string,
        args.maxResults as number | undefined
      );
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • XrayClient helper method: constructs JQL query for project test sets and delegates to searchTestSets GraphQL method.
    async getTestSetsByProject(projectKey: string, maxResults: number = 50): Promise<any> {
      const jql = `project = '${projectKey}'`;
      return this.searchTestSets(jql, maxResults);
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is a 'Get' operation, implying read-only behavior, but doesn't mention any constraints like pagination (despite the 'maxResults' parameter), rate limits, authentication requirements, or what happens if the project doesn't exist. The description adds minimal behavioral context beyond the basic action.

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 for a simple retrieval tool and front-loads the key information ('Get all test sets').

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 'test sets' are in this context, how results are structured, or any error conditions. For a tool with two parameters and no structured output documentation, more context is needed to help an agent use it effectively.

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, with clear documentation for both parameters ('projectKey' and 'maxResults'). The description doesn't add any meaningful parameter semantics beyond what's already in the schema—it mentions 'for a specific project' which aligns with 'projectKey' but provides no additional context about parameter usage or interactions.

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 ('Get') and resource ('all test sets for a specific project'), making the purpose understandable. However, it doesn't explicitly distinguish this tool from sibling tools like 'get_test_set' (singular) or 'search_test_sets', leaving some ambiguity about when to use this specific list-retrieval tool versus alternatives.

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 like 'get_test_set' (for a single test set) or 'search_test_sets' (for filtered searches). It mentions 'for a specific project' but doesn't clarify if this is the only way to get test sets or when other tools might be more appropriate.

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/c4m3lblue-star/xray-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server