Skip to main content
Glama
TCSoftInc

TestCollab MCP Server

by TCSoftInc

get_suite

Retrieve test suite details including title, description, and metadata by specifying a suite ID. Use this tool to access comprehensive information about specific test suites in TestCollab projects.

Instructions

Get details of a specific test suite by ID. Returns the suite's title, description, parent_id, and other metadata.

Required: id (suite ID) Optional: project_id

Input Schema

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

Implementation Reference

  • The handler function `handleGetSuite` executes the logic to fetch a test suite by ID from the API client.
    export async function handleGetSuite(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.getSuite(args.id, projectId);
    
        return {
          content: [
            {
              type: "text" as const,
              text: JSON.stringify({
                suite: result,
              }),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text" as const,
              text: JSON.stringify({
                error: {
                  code: "GET_SUITE_FAILED",
                  message:
                    error instanceof Error ? error.message : "Unknown error",
                },
              }),
            },
          ],
        };
      }
    }
  • The schema definition for the `get_suite` tool inputs.
    export const getSuiteSchema = z.object({
      id: z.number().describe("Suite ID to retrieve (required)"),
      project_id: z
        .number()
        .optional()
        .describe("Project ID (optional if TC_DEFAULT_PROJECT is set)"),
    });
  • The tool definition including its name and description.
    export const getSuiteTool = {
      name: "get_suite",
      description: `Get details of a specific test suite by ID.
    Returns the suite's title, description, parent_id, and other metadata.
    
    Required: id (suite ID)
    Optional: project_id`,
    };
Behavior3/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. It discloses return values (title, description, parent_id, metadata) which helps the agent understand the output structure, but omits safety properties (read-only status), error behaviors (e.g., invalid ID), or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action and efficiently structured in three sentences. However, the third sentence uses a slightly terse colon-separated format ('Required: id... Optional: project_id') that is less readable than natural language.

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

Completeness3/5

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

For a simple two-parameter getter without an output schema, the description is minimally adequate. It lists key return fields but vagueness around 'other metadata' and lack of error handling guidance leaves gaps given the absence of structured output schema.

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?

With 100% schema description coverage, the baseline is 3. The description summarizes the required/optional nature of parameters but adds no semantic detail beyond the schema (e.g., it omits the TC_DEFAULT_PROJECT context mentioned in the schema for project_id).

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 'Get details of a specific test suite by ID', providing a specific verb, resource, and scope. The 'by ID' qualifier effectively distinguishes this from the sibling list_suites tool.

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?

While the description implies usage by referencing 'specific test suite by ID', suggesting it requires a known identifier, it does not explicitly state when to use this versus list_suites or mention prerequisites like needing the suite ID beforehand.

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