Skip to main content
Glama

Fetch test execution results

wopee_fetch_executed_test_cases

Retrieve executed test case results from an analysis suite, including status, agent report, and code report. Call after dispatching the agent to check progress or completion.

Instructions

Retrieve results of test cases executed by the autonomous agent. Returns each test case with its execution status (IN_PROGRESS, FINISHED, FAILED), agent report (natural language findings), and code report (technical details). Read-only: does not trigger any execution. Use this after wopee_dispatch_agent to check results — if status is IN_PROGRESS, wait and call again. Requires suite UUID. Optionally accepts an analysis identifier (e.g. A068, found in suite data) to filter to a specific analysis run. Returns an empty array if no test cases have been executed in this suite. Do NOT use this to fetch test artifacts like user stories or code — use wopee_fetch_artifact for that.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
suiteUuidYesUUID of the analysis suite to fetch executed test cases for
analysisIdentifierNoAnalysis identifier of the suite (ex. A068). Can be found in the analysis suite data.

Implementation Reference

  • Main tool definition and handler for wopee_fetch_executed_test_cases. The handler takes a suiteUuid (and optional analysisIdentifier), creates the input via factory, sends a GraphQL request to fetch executed test cases, and returns the results as JSON.
    import {
      WopeeFetchExecutedTestCasesInput,
      WopeeFetchExecutedTestCasesInputSchema,
      FetchExecutedTestCasesInputSchema,
    } from "./schema.js";
    import { FetchExecutedTestCasesResponse, ToolName } from "../shared/types.js";
    import { _parseError } from "../shared/helpers.js";
    import { createFetchExecutedTestCasesInput } from "./factory.js";
    import { FetchExecutedTestCases } from "../shared/gql-queries.js";
    import { requestClient } from "../../utils/requestClient.js";
    
    export const wopeeFetchExecutedTestCases = {
      name: ToolName.WOPEE_FETCH_EXECUTED_TEST_CASES,
      config: {
        title: "Fetch test execution results",
        description:
          "Retrieve results of test cases executed by the autonomous agent. Returns each test case with its execution status (IN_PROGRESS, FINISHED, FAILED), agent report (natural language findings), and code report (technical details). Read-only: does not trigger any execution. Use this after wopee_dispatch_agent to check results — if status is IN_PROGRESS, wait and call again. Requires suite UUID. Optionally accepts an analysis identifier (e.g. A068, found in suite data) to filter to a specific analysis run. Returns an empty array if no test cases have been executed in this suite. Do NOT use this to fetch test artifacts like user stories or code — use wopee_fetch_artifact for that.",
        inputSchema: WopeeFetchExecutedTestCasesInputSchema.shape,
      },
      handler: async (input: WopeeFetchExecutedTestCasesInput) => {
        try {
          const factoryInput = createFetchExecutedTestCasesInput(input);
          const parsedInput =
            FetchExecutedTestCasesInputSchema.parse(factoryInput);
    
          const result = await requestClient<{
            fetchExecutedTestCases: FetchExecutedTestCasesResponse[];
          }>(FetchExecutedTestCases, {
            input: parsedInput,
          });
    
          if (!result?.fetchExecutedTestCases)
            return {
              content: [
                {
                  type: "text" as const,
                  text: "Failed to fetch executed test cases: no data returned",
                },
              ],
            };
    
          return {
            content: [
              {
                type: "text" as const,
                text: JSON.stringify(result.fetchExecutedTestCases, null, 2),
              },
            ],
          };
        } catch (error) {
          return _parseError(error);
        }
      },
    };
  • Zod schemas for the tool. WopeeFetchExecutedTestCasesInputSchema defines the public input (suiteUuid required, analysisIdentifier optional). FetchExecutedTestCasesInputSchema adds projectUuid for internal use.
    import { z } from "zod";
    
    export const WopeeFetchExecutedTestCasesInputSchema = z.object({
      suiteUuid: z
        .string({
          description: "UUID of the analysis suite to fetch executed test cases for",
        })
        .min(1, "Suite UUID is required"),
      analysisIdentifier: z
        .string({
          description:
            "Analysis identifier of the suite (ex. A068). Can be found in the analysis suite data.",
        })
        .optional(),
    });
    
    export const FetchExecutedTestCasesInputSchema = z.object({
      projectUuid: z.string().min(1, "Project UUID is required"),
      analysisSuiteUuid: z.string().min(1, "Suite UUID is required"),
      analysisIdentifier: z.string().optional(),
    });
    
    export type WopeeFetchExecutedTestCasesInput = z.infer<
      typeof WopeeFetchExecutedTestCasesInputSchema
    >;
    export type FetchExecutedTestCasesInput = z.infer<
      typeof FetchExecutedTestCasesInputSchema
    >;
  • Tool registration: imports wopeeFetchExecutedTestCases from its directory and exports it in the TOOLS array.
    import { wopeeFetchArtifact } from "./wopee_fetch_artifact/index.js";
    import { wopeeUpdateArtifact } from "./wopee_update_artifact/index.js";
    import { wopeeGenerateArtifact } from "./wopee_generate_artifact/index.js";
    import { wopeeDispatchAgent } from "./wopee_dispatch_agent/index.js";
    import { wopeeDispatchAnalysis } from "./wopee_dispatch_analysis/index.js";
    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,
  • Enum definition ToolName.WOPEE_FETCH_EXECUTED_TEST_CASES = 'wopee_fetch_executed_test_cases', used as the tool's name identifier.
    export enum ToolName {
      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",
    }
  • Factory function createFetchExecutedTestCasesInput that enriches user input with WOPEE_PROJECT_UUID from config to create the internal request input.
    import { getConfig } from "../../utils/getConfig.js";
    import {
      FetchExecutedTestCasesInput,
      WopeeFetchExecutedTestCasesInput,
    } from "./schema.js";
    
    export const createFetchExecutedTestCasesInput = (
      input: WopeeFetchExecutedTestCasesInput,
    ): FetchExecutedTestCasesInput => {
      const { WOPEE_PROJECT_UUID } = getConfig();
      if (!WOPEE_PROJECT_UUID) throw new Error("WOPEE_PROJECT_UUID is not set");
    
      return {
        projectUuid: WOPEE_PROJECT_UUID,
        analysisSuiteUuid: input.suiteUuid,
        ...(input.analysisIdentifier
          ? { analysisIdentifier: input.analysisIdentifier }
          : {}),
      };
    };
Behavior5/5

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

No annotations provided, but description declares read-only nature, mentions empty array return, and fully describes behavioral traits without contradiction.

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?

Concise with no wasted sentences. Front-loaded with purpose and progressively adds detail.

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?

Covers return values, edge cases (empty array), and interaction steps despite no output schema. Complete for a tool with 2 parameters.

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?

Schema coverage is 100%, baseline 3. Description adds value for analysisIdentifier by specifying format (ex. A068) and source (found in suite data), going beyond 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?

Description clearly states it retrieves results of test cases executed by the autonomous agent. It specifies return fields (status, agent report, code report) and distinguishes from sibling tool wopee_fetch_artifact.

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 says to use after wopee_dispatch_agent, advises waiting if IN_PROGRESS, and explicitly warns against using for artifacts, directing to alternative.

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