Skip to main content
Glama
debugg-ai

Debugg AI MCP

Official
by debugg-ai

Search Test Suites

search_test_suites

Search and list test suites for a project, with paginated results showing suite status, test counts, pass rates, and last run timestamps. Specify a project UUID or name, optionally filter by text.

Instructions

List and search test suites for a project. Returns paginated results with suite status, test counts, pass rates, and last run timestamps. Requires a project identifier (projectUuid or projectName). Optional: search text filter, page, pageSize (1-100, default 20).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectUuidNoProject UUID. Provide projectUuid OR projectName.
projectNameNoProject name (case-insensitive exact match). Provide projectUuid OR projectName.
searchNoOptional text filter applied to suite name and description.
pageNoPage number (default 1).
pageSizeNoResults per page (default 20, max 100).

Implementation Reference

  • Main handler function that executes the search_test_suites tool logic. It creates a DebuggAIServerClient, resolves projectUuid (via projectName if needed), calls client.listTestSuites() with search/pagination params, and returns the JSON result.
    export async function searchTestSuitesHandler(
      input: SearchTestSuitesInput,
      _context: ToolContext,
    ): Promise<ToolResponse> {
      const start = Date.now();
      logger.toolStart('search_test_suites', 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 as any).candidates });
          projectUuid = resolved.uuid;
        }
    
        const result = await client.listTestSuites({
          projectUuid,
          search: input.search,
          page: input.page,
          pageSize: input.pageSize,
        });
    
        logger.toolComplete('search_test_suites', Date.now() - start);
        return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
      } catch (error) {
        logger.toolError('search_test_suites', error as Error, Date.now() - start);
        throw handleExternalServiceError(error, 'DebuggAI', 'search_test_suites');
      }
    }
  • Zod schema and TypeScript type for the search_test_suites input (projectIdentifier, optional search, page, pageSize).
    export const SearchTestSuitesInputSchema = z.object({
      ...projectIdentifier,
      search: z.string().optional(),
      page: z.number().int().min(1).optional(),
      pageSize: z.number().int().min(1).max(100).optional(),
    }).strict();
    
    export type SearchTestSuitesInput = z.infer<typeof SearchTestSuitesInputSchema>;
  • Builds the Tool object with name 'search_test_suites', title, description, and inputSchema (with PROJECT_PROPS, search, page, pageSize).
    export function buildSearchTestSuitesTool(): Tool {
      return {
        name: 'search_test_suites',
        title: 'Search Test Suites',
        description: 'List and search test suites for a project. Returns paginated results with suite status, test counts, pass rates, and last run timestamps. Requires a project identifier (projectUuid or projectName). Optional: search text filter, page, pageSize (1-100, default 20).',
        inputSchema: {
          type: 'object',
          properties: {
            ...PROJECT_PROPS,
            search: { type: 'string', description: 'Optional text filter applied to suite name and description.' },
            page: { type: 'number', description: 'Page number (default 1).', minimum: 1 },
            pageSize: { type: 'number', description: 'Results per page (default 20, max 100).', minimum: 1, maximum: 100 },
          },
          additionalProperties: false,
        },
      };
    }
  • Builds the ValidatedTool combining the Tool definition with the Zod schema and the handler function.
    export function buildValidatedSearchTestSuitesTool(): ValidatedTool {
      return { ...buildSearchTestSuitesTool(), inputSchema: SearchTestSuitesInputSchema, handler: searchTestSuitesHandler };
    }
  • tools/index.ts:49-49 (registration)
    Registration of search_test_suites tool in the main tools array (initTools function).
    buildSearchTestSuitesTool(),
Behavior3/5

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

With no annotations, the description carries the full burden. It implies a read-only operation (list and search) and describes returned data, but does not explicitly state whether the tool has side effects, requires authentication, or has rate limits. The description adds some context but leaves gaps.

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?

Three sentences, front-loaded with purpose, no wasted words. Each sentence adds necessary information: what it does, what it requires, and what is optional.

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?

For a tool with 5 parameters, no output schema, and no annotations, the description covers purpose, required inputs, optional parameters with constraints, and return fields. It lacks mention of default page number (1) and sorting, but these are minor omissions for a list/search tool.

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?

The schema has 100% coverage, so baseline is 3. The description adds value by clarifying that projectUuid and projectName are mutually exclusive, and by providing range/limits for pageSize (1-100, default 20). This goes beyond individual 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?

The description clearly states the verb (list and search), the resource (test suites), and the return data (status, counts, rates, timestamps). It distinguishes from sibling tools like search_executions and search_projects by specifying the resource type.

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 explains required inputs (projectUuid or projectName) and optional parameters (search, page, pageSize) with limits. However, it does not explicitly compare with alternatives or state when not to use this tool, missing a chance to fully differentiate from siblings like get_test_suite_results.

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