Skip to main content
Glama

Create blank analysis suite

wopee_create_blank_suite

Creates a new empty analysis suite in the current project. Returns the suite UUID required for subsequent test generation and artifact management steps.

Instructions

Create a new empty analysis suite in the current project. Use this as the first step when you want to manually build a test suite — the returned suite UUID is needed by wopee_generate_artifact, wopee_fetch_artifact, wopee_update_artifact, and wopee_dispatch_agent. If you want to auto-analyze a web app instead, use wopee_dispatch_analysis which creates and populates a suite in one step. Takes no input parameters; uses WOPEE_PROJECT_UUID from environment. Not idempotent: each call creates a new suite. Returns the suite object with UUID, name, type, and status. Fails if WOPEE_PROJECT_UUID is not configured.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the tool logic. Reads WOPEE_PROJECT_UUID from config, sends a GraphQL mutation (CreateBlankAnalysisSuite) to create a blank analysis suite, and returns the created suite object as JSON. Returns an error if project UUID is missing or the API returns no data.
      handler: async () => {
        try {
          const { WOPEE_PROJECT_UUID } = getConfig();
    
          if (!WOPEE_PROJECT_UUID)
            return {
              content: [
                {
                  type: "text" as const,
                  text: "WOPEE_PROJECT_UUID is not set",
                },
              ],
            };
    
          const result = await requestClient<{
            createBlankAnalysisSuite: AnalysisSuite;
          }>(CreateBlankAnalysisSuite, {
            projectUuid: WOPEE_PROJECT_UUID,
          });
    
          if (!result?.createBlankAnalysisSuite)
            return {
              content: [
                {
                  type: "text" as const,
                  text: "Failed to create blank suite: no data returned",
                },
              ],
            };
    
          return {
            content: [
              {
                type: "text" as const,
                text: JSON.stringify(result.createBlankAnalysisSuite, null, 2),
              },
            ],
          };
        } catch (error) {
          return _parseError(error);
        }
      },
    };
  • Enum registration of the tool name 'wopee_create_blank_suite' (ToolName.WOPEE_CREATE_BLANK_SUITE).
      WOPEE_CREATE_BLANK_SUITE = "wopee_create_blank_suite",
      WOPEE_FETCH_ANALYSIS_SUITES = "wopee_fetch_analysis_suites",
      WOPEE_FETCH_EXECUTED_TEST_CASES = "wopee_fetch_executed_test_cases",
    
      WOPEE_DISPATCH_ANALYSIS = "wopee_dispatch_analysis",
      WOPEE_DISPATCH_AGENT = "wopee_dispatch_agent",
    
      WOPEE_FETCH_ARTIFACT = "wopee_fetch_artifact",
      WOPEE_UPDATE_ARTIFACT = "wopee_update_artifact",
      WOPEE_GENERATE_ARTIFACT = "wopee_generate_artifact",
    
      WOPEE_SEND_CHAT_MESSAGE = "wopee_send_chat_message",
      WOPEE_READ_CHAT_HISTORY = "wopee_read_chat_history",
      WOPEE_CREATE_GITHUB_ISSUE = "wopee_create_github_issue",
    }
  • Type definition for AnalysisSuite, describing the return shape of createBlankAnalysisSuite including uuid, name, suiteType, executionStatus, etc.
    export type AnalysisSuite = {
      uuid: string;
      name: string | null;
      suiteType: SuiteType | null;
      executionStatus: ExecutionStatus | null;
      analysisIdentifier: string | null;
      suiteRunningStatus: SuiteRunningStatus | null;
      createdAt: string;
      updatedAt: string;
      generatedAnalysisDataState: GeneratedAnalysisDataState | null;
    };
  • Import and registration of the tool in the TOOLS array (line 14).
    import { wopeeCreateBlankSuite } from "./wopee_create_blank_suite/index.js";
    import { wopeeFetchAnalysisSuites } from "./wopee_fetch_analysis_suites/index.js";
    import { wopeeFetchExecutedTestCases } from "./wopee_fetch_executed_test_cases/index.js";
    import { wopeeSendChatMessage } from "./wopee_send_chat_message/index.js";
    import { wopeeReadChatHistory } from "./wopee_read_chat_history/index.js";
    import { wopeeCreateGithubIssue } from "./wopee_create_github_issue/index.js";
    
    export const TOOLS = [
      wopeeCreateBlankSuite,
      wopeeFetchAnalysisSuites,
      wopeeFetchExecutedTestCases,
    
      wopeeDispatchAnalysis,
      wopeeDispatchAgent,
    
      wopeeFetchArtifact,
      wopeeUpdateArtifact,
      wopeeGenerateArtifact,
    
      wopeeSendChatMessage,
      wopeeReadChatHistory,
      wopeeCreateGithubIssue,
    ];
  • Import of CreateBlankAnalysisSuite GraphQL query from shared/gql-queries.js and _parseError from helpers.
    import { CreateBlankAnalysisSuite } from "../shared/gql-queries.js";
Behavior5/5

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

Discloses that the tool is not idempotent (each call creates a new suite), uses the WOPEE_PROJECT_UUID environment variable, returns a suite object with specific fields, and fails if the environment variable is not configured. No annotations are provided, so the description fully covers behavioral aspects.

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?

Four sentences, each packed with essential information. Front-loaded with purpose and immediate usage context. No wasted words; every sentence serves a clear function.

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

Completeness5/5

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

Given the simple schema (no parameters, no output schema) and the presence of sibling tools, the description thoroughly covers purpose, usage context, behavioral traits, parameter details, return value, and failure conditions. It is fully self-contained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema is empty, and the description adds significant meaning by stating that no input parameters are required, that it uses WOPEE_PROJECT_UUID from environment, and that it returns a suite object with UUID, name, type, and status. This exceeds the baseline expectation for zero-parameter tools.

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 tool creates a new empty analysis suite, using the verb 'create' and the resource 'analysis suite'. It distinguishes itself from the sibling tool wopee_dispatch_analysis by specifying that this is for manual building while the other auto-populates.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states to use this as the first step for manually building a test suite, and provides an alternative: wopee_dispatch_analysis for auto-analysis. It also lists tools that depend on the returned suite UUID.

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/Wopee-io/wopee-mcp'

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