Skip to main content
Glama
debugg-ai

Debugg AI MCP

Official
by debugg-ai

Create Test Suite

create_test_suite

Create a named test suite for your project. Provide name, description, and project UUID or name. Returns suite details including UUID, name, description, run status, and test count.

Instructions

Create a named test suite for a project. A test suite is a collection of test cases that can be run together. Requires name, description, and a project identifier (projectUuid or projectName). Returns {uuid, name, description, runStatus, testsCount}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesSuite name. Required.
descriptionYesSuite description. Required.
projectUuidNoProject UUID. Provide projectUuid OR projectName.
projectNameNoProject name (case-insensitive exact match). Provide projectUuid OR projectName.

Implementation Reference

  • Main handler function for the 'create_test_suite' tool. Validates input, resolves project UUID (by UUID or name via resolveProject), calls DebuggAIServerClient.createTestSuite API, and returns the created suite JSON.
    export async function createTestSuiteHandler(
      input: CreateTestSuiteInput,
      _context: ToolContext,
    ): Promise<ToolResponse> {
      const start = Date.now();
      logger.toolStart('create_test_suite', input);
      try {
        const client = new DebuggAIServerClient(config.api.key);
        await client.init();
    
        let projectUuid = input.projectUuid;
        if (!projectUuid) {
          const resolved = await resolveProject(client, input.projectName!);
          if ('error' in resolved) return errorResp(resolved.error, resolved.message, { candidates: resolved.candidates });
          projectUuid = resolved.uuid;
        }
    
        const suite = await client.createTestSuite({ name: input.name, description: input.description, projectUuid });
        logger.toolComplete('create_test_suite', Date.now() - start);
        return { content: [{ type: 'text', text: JSON.stringify(suite, null, 2) }] };
      } catch (error) {
        logger.toolError('create_test_suite', error as Error, Date.now() - start);
        throw handleExternalServiceError(error, 'DebuggAI', 'create_test_suite');
      }
    }
  • Zod schema and TypeScript type for create_test_suite input validation. Requires name, description, and optionally projectUuid or projectName.
    export const CreateTestSuiteInputSchema = z.object({
      name: z.string().min(1),
      description: z.string().min(1),
      ...projectIdentifier,
    }).strict();
    
    export type CreateTestSuiteInput = z.infer<typeof CreateTestSuiteInputSchema>;
  • Tool definition builder: registers the tool with name 'create_test_suite', title, description, and inputSchema. Also exports buildValidatedCreateTestSuiteTool which pairs the schema with the handler.
    export function buildCreateTestSuiteTool(): Tool {
      return {
        name: 'create_test_suite',
        title: 'Create Test Suite',
        description: 'Create a named test suite for a project. A test suite is a collection of test cases that can be run together. Requires name, description, and a project identifier (projectUuid or projectName). Returns {uuid, name, description, runStatus, testsCount}.',
        inputSchema: {
          type: 'object',
          properties: {
            name: { type: 'string', description: 'Suite name. Required.', minLength: 1 },
            description: { type: 'string', description: 'Suite description. Required.', minLength: 1 },
            ...PROJECT_PROPS,
          },
          required: ['name', 'description'],
          additionalProperties: false,
        },
      };
    }
    
    export function buildValidatedCreateTestSuiteTool(): ValidatedTool {
      return { ...buildCreateTestSuiteTool(), inputSchema: CreateTestSuiteInputSchema, handler: createTestSuiteHandler };
    }
  • tools/index.ts:48-85 (registration)
    Registration of create_test_suite in the global tool registry via initTools (line 48 for Tool, line 70 for ValidatedTool).
        buildCreateTestSuiteTool(),
        buildSearchTestSuitesTool(),
        buildDeleteTestSuiteTool(),
        buildCreateTestCaseTool(),
        buildUpdateTestCaseTool(),
        buildDeleteTestCaseTool(),
        buildRunTestSuiteTool(),
        buildGetTestSuiteResultsTool(),
      ];
      const validated: ValidatedTool[] = [
        buildValidatedTestPageChangesTool(ctx),
        buildValidatedTriggerCrawlTool(ctx),
        buildValidatedProbePageTool(),
        buildValidatedSearchProjectsTool(),
        buildValidatedSearchEnvironmentsTool(),
        buildValidatedCreateEnvironmentTool(),
        buildValidatedUpdateEnvironmentTool(),
        buildValidatedDeleteEnvironmentTool(),
        buildValidatedUpdateProjectTool(),
        buildValidatedDeleteProjectTool(),
        buildValidatedSearchExecutionsTool(),
        buildValidatedCreateProjectTool(),
        buildValidatedCreateTestSuiteTool(),
        buildValidatedSearchTestSuitesTool(),
        buildValidatedDeleteTestSuiteTool(),
        buildValidatedCreateTestCaseTool(),
        buildValidatedUpdateTestCaseTool(),
        buildValidatedDeleteTestCaseTool(),
        buildValidatedRunTestSuiteTool(),
        buildValidatedGetTestSuiteResultsTool(),
      ];
    
      _tools = tools;
      _validatedTools = validated;
    
      toolRegistry.clear();
      for (const v of validated) toolRegistry.set(v.name, v);
    }
  • DebuggAIServerClient.createTestSuite method: makes the actual HTTP POST to 'api/v1/test-suites/' API endpoint to create the test suite.
    public async createTestSuite(input: {
      name: string;
      description: string;
      projectUuid: string;
    }): Promise<{ uuid: string; name: string; description: string | null; runStatus: string; testsCount: number }> {
      if (!this.tx) throw new Error('Client not initialized — call init() first');
      const s = await this.tx.post<any>('api/v1/test-suites/', {
        name: input.name,
        description: input.description,
        project: input.projectUuid,
      });
      return this.mapTestSuite(s);
    }
Behavior3/5

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

No annotations, so description must shoulder burden. It mentions return fields but does not disclose side effects, required project existence, or error conditions. Adequate but not thorough.

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?

Two sentences with front-loaded purpose, no wasted words. Every sentence adds value.

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?

Covers creation purpose, required fields, and return format. Lacks details on duplicate handling or project existence checks, but sufficient for a simple creation tool.

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 baseline 3. Description restates that projectUuid or projectName is needed, adding minimal value over schema descriptions.

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?

Clearly states it creates a named test suite for a project, defines what a test suite is, and distinguishes from sibling creation tools like create_test_case.

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?

Specifies required inputs (name, description, project identifier) but does not explicitly state when not to use or compare to alternatives; it is clear enough for typical usage.

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/debugg-ai/debugg-ai-mcp'

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