Skip to main content
Glama
TCSoftInc

TestCollab MCP Server

by TCSoftInc

delete_suite

Remove a test suite from TestCollab to manage testing resources. This action deletes the suite and may affect related child suites and test cases.

Instructions

Delete a test suite from TestCollab.

WARNING: This will delete the suite and may affect child suites and test cases. Use with caution.

Required: id (suite ID) Optional: project_id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSuite ID to delete (required)
project_idNoProject ID (optional if TC_DEFAULT_PROJECT is set)

Implementation Reference

  • The handle function for the delete_suite tool which uses the API client to perform the deletion and clears the project cache.
    export async function handleDeleteSuite(args: {
      id: number;
      project_id?: number;
    }): Promise<{ content: Array<{ type: "text"; text: string }> }> {
      try {
        const projectId = resolveProjectId(args.project_id);
        if (!projectId) {
          return {
            content: [
              {
                type: "text" as const,
                text: JSON.stringify({
                  error: {
                    code: "MISSING_PROJECT_ID",
                    message:
                      "No project_id provided and no default project configured. Set TC_DEFAULT_PROJECT or pass project_id.",
                  },
                }),
              },
            ],
          };
        }
    
        const client = getApiClient();
        const result = await client.deleteSuite(args.id, projectId);
    
        // Invalidate project context cache
        clearProjectContextCache();
    
        return {
          content: [
            {
              type: "text" as const,
              text: JSON.stringify({
                success: true,
                deleted_suite_id: args.id,
                result,
              }),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text" as const,
              text: JSON.stringify({
                error: {
                  code: "DELETE_SUITE_FAILED",
                  message:
                    error instanceof Error ? error.message : "Unknown error",
                },
              }),
            },
          ],
        };
      }
    }
  • Input validation schema for the delete_suite tool.
    export const deleteSuiteSchema = z.object({
      id: z.number().describe("Suite ID to delete (required)"),
      project_id: z
        .number()
        .optional()
        .describe("Project ID (optional if TC_DEFAULT_PROJECT is set)"),
    });
  • Tool definition for delete_suite with its name and description.
    export const deleteSuiteTool = {
      name: "delete_suite",
      description: `Delete a test suite from TestCollab.
    
    WARNING: This will delete the suite and may affect child suites and test cases. Use with caution.
    
    Required: id (suite ID)
    Optional: project_id`,
    };
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses critical cascade behavior (child suites/test cases affected) which is beyond schema. Missing: return value description, error handling (404 if ID not found?), or idempotency details.

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 distinct sections: purpose statement, behavioral warning, parameter summary. Front-loaded with intent, no filler text. Every sentence earns its place; WARNING format appropriately emphasizes destructive nature.

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?

Adequate for a 2-parameter destructive operation with cascade implications. Covers primary risk (child deletion) and required inputs. Lacks output description (absent schema) and specific error scenarios, but sufficient for safe invocation.

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 applies. Description repeats parameter requirements ('Required: id', 'Optional: project_id') but adds minimal semantic value beyond schema descriptions. The '(suite ID)' clarification for id is mildly helpful but redundant with schema.

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?

Opens with specific verb (Delete) + resource (test suite) + system (TestCollab). The warning about affecting child suites and test cases clarifies scope, distinguishing it from sibling tools like update_suite or move_suite.

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?

Provides 'Use with caution' warning implying when to be careful (cascade effects), but lacks explicit when-to-use vs alternatives (e.g., no mention of update_suite as alternative to modification, or prerequisites like permissions).

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/TCSoftInc/testcollab-mcp-server'

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