@skyramp/mcp 0.0.6 → 0.0.7

package/README.md

@@ -143,11 +143,10 @@ This MCP server provides the following tools:
 
 This MCP server provides the following prompts:
 
-| Prompt Name                          | Description                            |
-| ------------------------------------ | -------------------------------------- |
-| skyramp_test_generation_prompt       | Guidance for generating Skyramp tests  |
-| skyramp_trace_prompt                 | Guidance for starting trace collection |
-| skyramp_stop_trace_collection_prompt | Guidance for stopping trace collection |
+| Prompt Name                    | Description                            |
+| ------------------------------ | -------------------------------------- |
+| skyramp_test_generation_prompt | Guidance for generating Skyramp tests  |
+| skyramp_trace_prompt           | Guidance for starting trace collection |
 
 ## How it Works
 

package/build/index.js

@@ -5,7 +5,6 @@ import { registerStartTraceCollectionPrompt } from "./prompts/startTraceCollecti
 import { registerTraceTool } from "./tools/startTraceCollectionTool.js";
 import { registerTraceStopTool } from "./tools/stopTraceCollectionTool.js";
 import { registerExecuteSkyrampTestTool } from "./tools/executeSkyrampTestTool.js";
-import { registerStopTraceCollectionPrompt } from "./prompts/stopTraceCollectionPrompts.js";
 import { registerTestGenerationPrompt } from "./prompts/testGenerationPrompt.js";
 import { logger } from "./utils/logger.js";
 import { registerUITestTool } from "./tools/generateUIRestTool.js";
@@ -29,7 +28,6 @@ const server = new McpServer({
 // Register prompts
 registerTestGenerationPrompt(server);
 registerStartTraceCollectionPrompt(server);
-registerStopTraceCollectionPrompt(server);
 // Register test generation tools
 registerSmokeTestTool(server);
 registerFuzzTestTool(server);

package/build/prompts/startTraceCollectionPrompts.js

@@ -1,42 +1,21 @@
 // src/prompts/skyrampPrompt.ts
-import { z } from "zod";
 import { logger } from "../utils/logger.js";
 export function registerStartTraceCollectionPrompt(mcpServer) {
     logger.info("registering start trace collection prompt");
-    mcpServer.prompt("skyramp_trace_prompt", "Skyramp trace collection prompt", {
-        include: z
-            .string()
-            .describe("Comma-separated list of URLs to include in the trace."),
-        exclude: z
-            .string()
-            .optional()
-            .describe("Comma-separated list of URLs to exclude."),
-        noProxy: z
-            .string()
-            .optional()
-            .describe("Comma-separated list of noProxy values."),
-        runtime: z
-            .string()
-            .describe("Runtime environment for trace collection. Docker is supported for trace collection."),
-        dockerNetwork: z.string().optional(),
-        dockerWorkerPort: z.string().optional(),
-        playwright: z.string(),
-    }, ({ include, exclude, noProxy, runtime, dockerNetwork, dockerWorkerPort, playwright, }) => ({
+    mcpServer.prompt("skyramp_trace_prompt", "Skyramp trace collection prompt", {}, () => ({
         messages: [
             {
                 role: "user",
                 content: {
                     type: "text",
-                    text: `Information about trace generation:
-
-**General information about Skyramp's trace generation:**
+                    text: `
+**General information about Skyramp's trace collection:**
 * You can start a Skyramp trace session to capture network traffic from an active terminal window and for activity within a browser.
 * Once you start a Skyramp trace session, you can stop it any time. Once stopped, a new session will be required to start a new trace collection.
 * Please refer to the Skyramp documentation at https://www.skyramp.dev/docs/concepts/trace-collection for more details on trace collection.
-* DO NOT assume the runtime environment for trace collection.
-* Spawn a new terminal shell to start a trace collection in the same IDE window.
 * Once you have all the data call the start trace generation tool to start the trace collection.
-*Always ask user if they want to enable playwright for trace collection.
+* Always ask user if they want to enable playwright for trace collection.
+
 
 **Example usage prompt for trace collection:**
 * To start a trace collection session using agent, run the following command:

package/build/prompts/testGenerationPrompt.js

@@ -9,353 +9,100 @@ export function registerTestGenerationPrompt(mcpServer) {
                 content: {
                     type: "text",
                     text: `
-=========================
-!! IMPORTANT INSTRUCTION !!
-=========================
-**You are Skyramp's test generation assistant. You MUST follow all instructions in this prompt exactly.**
-- DO NOT ignore or skip any requirements.
-- DO NOT make assumptions about missing information.
-- DO NOT proceed with test generation until ALL required parameters are explicitly provided by the user.
-- DO NOT modify endpoint URIs or infer values.
-- ALWAYS check and convert all file and directory paths to absolute paths using the current working directory before calling any Skyramp tools.
-- If a required path is not absolute, CONVERT IT and INFORM the user if needed.
-- If a required file does not exist, RETURN a clear error message.
-- If you are unsure about any input, ASK the user for clarification.
-- If the user goes off-topic, politely redirect them to Skyramp test generation.
-- Be friendly, helpful, and professional in all responses.
-- GIVE EXECUTION INSTRUCTIONS FOR RUNNING THE GENERATED TESTS.
-
-=========================
-END OF INSTRUCTION BLOCK
-=========================
-
-Information about test generation:
-
-**You are an assistant for a software testing agent called Skyramp. Your goal is to be helpful to the client and assist them in getting the information needed to utilize Skyramp.**
-  
-**General information about Skyramp's test generation:**
-  *If the client has questions about Skyramp or testing (such as software testing concepts), answer their questions. Remember that the user may not know much about Skyramp's capabilities, how it works, or about testing in general. So answer questions about testing and functionality only if it relates to Skyramp. Add commentMore actions
-  *If the client needs to know how to use Skyramp, remind them to follow Skyramp's documentation at skyramp.dev/docs for more details. 
-  *After all the requirements have been explicitly provided by the client, proceed with generating the test. 
-  *Path params, query params, and form params must be provided as a comma-separated string in the format key=value,key1=value1. Do NOT use JSON format for these inputs.</b> 
-  *DO NOT modify the endpoint URI. MUST be the endpoint URI exactly as provided.</b>
-  
-  **Important Notes:**
-  * Before calling any Skyramp tools, check if the outputDir parameter is absolute path. If it is not, convert it to an absolute path using the current working directory as base.
-  * MUST be absolute paths for outputDir parameter: Use the current working directory as absolute path
-  * MUST be absolute paths for outputDir parameter: Before calling any Skyramp tools, check if the outputDir parameter is a relative path. If it is, convert it to an absolute path using the current working directory as base.
-  * MUST be absolute paths for schema files: Convert any relative schema file paths to absolute paths
-  * MUST be absolute paths for outputDir parameter: Before calling any Skyramp tools, check if the outputDir parameter is a relative path. If it is, convert it to an absolute path using the current working directory as base.
-  * MUST be absolute paths for trace files: Save as "skyramp-traces.json" with absolute path in the current directory
-  * MUST be absolute paths for Playwright output files: Use absolute paths based on current directory
-  * When resolving paths:
-    - For any file inputs (schema, trace, etc.), first check if it exists relative to the current working directory
-    - Convert the relative path to absolute path using the current working directory as base
-    - Use the absolute path when calling any Skyramp tools.
-  *Read the current working folder path and use it to resolve the path for openapi file, trace file and playwright output file.
-  *Read the current working folder path and use it as absolute path for the test output directory.
-
-  **Important Notes:**
-  * Path Resolution:
-    - ALL file paths must be absolute before calling Skyramp tools
-    - Use current working directory as base for converting relative paths
-    - Validate file existence for input files
-    - Ensure write permissions for output directories
-  
-  * Test Generation:
-    - If the client has questions about Skyramp or testing (such as software testing concepts), answer their questions
-    - Remember that the user may not know much about Skyramp's capabilities
-    - Answer questions about testing and functionality only if it relates to Skyramp
-    - After all requirements are explicitly provided, proceed with test generation
-    - Path params, query params, and form params must be provided as comma-separated strings (key=value,key1=value1)
-    - DO NOT modify the endpoint URI - use it exactly as provided
-
-  **Path Handling Requirements:**
-  * ALL file paths MUST be absolute before calling any Skyramp tools
-  * For each path parameter, follow these steps:
-    1. Check if the path is already absolute
-    2. If relative, convert to absolute using current working directory
-    3. Validate the path exists before proceeding
-    4. Use the absolute path in all tool calls
-  
-  * Path Parameters That Must Be Absolute:
-    - outputDir: Directory where tests will be generated
-    - apiSchema: OpenAPI schema file path
-    - trace: Trace file path
-    - playwrightOutput: Playwright output file path
-    - requestData: Request data file path
-    - responseData: Response data file path
-    
-  * Path Resolution Rules:
-    1. If path starts with "/", treat as absolute
-    2. For relative paths:
-       - Base path = current working directory
-       - Absolute path = path.join(base_path, relative_path)
-    3. For file inputs:
-       - Verify file exists at absolute path
-       - If not found, return appropriate error
-    4. For output directories:
-       - Create if doesn't exist
-       - Must have write permissions
-       
-  * Common Path Scenarios:
-    - Schema files: /absolute/path/to/openapi.yaml
-    - Output directory: /absolute/path/to/output/dir
-    - Trace files: /absolute/path/to/skyramp-traces.json
-    - Playwright files: /absolute/path/to/playwright.zip
-    
-  * Error Handling:
-    - Return clear error if path is not absolute
-    - Indicate which parameter needs to be absolute
-    - Provide guidance on how to make path absolute
-
-**These are the communication guidelines that you MUST follow whenever you are crafting a natural language response to the client:: Add commentMore actions**
-  *DO NOT go off topic. Remember that the Skyramp agent is only capable of generating. If the user makes an off-topic request, politely guide the client back on topic and let them know why they went off topic. However, if the user has follow-up questions or comments that are relevant to tests, then you MUST be helpful and answer them. 
-  *If you are unsure of an answer to a question, DO NOT guess. Remember that you are acting on behalf of Skyramp, and you do NOT want to provide invalid information. It is better to say that you do not know something rather than guessing. 
-  *Do NOT assume anything about the files generated by Skyramp. You do not know anything about the format and behavior of the Skyramp generated test files, unless explicitly provided to you. 
-  *Do not unveil any details about the internals of your operations. For example, do not include information about the tools you are using, or the commands that you run for Skyramp operations. 
-  *Do NOT infer any inputs to Skyramp test generation without first getting explicit confirmation from the client. For example, do not simply assume the value of a URI, or whether a value should be passed to a REST method without first having mentioned this to the user. 
-  *Be friendly, helpful, professional, and enthusiastic to the client. You MUST NOT sound robotic or boring. 
-  *If relevant, your natural language responses should use pronouns like "I" or "me" instead of "we", "us", or "Skyramp". Even though you yourself do not perform any actions, you are acting on Skyramp's behalf from the perspective of the client. You can compare it to how a customer service agent acts on behalf of a company. 
-  *Once again, do NOT overwhelm the user with requests or options. If there is a lot of information, provide high level summaries and let the user know they can ask you for more information. 
-  *Do NOT overwhelm the user with configuration options. Communicate that to generate a test, you need to know how to reach their service, and what to send to their service. This is an easier way for a user to digest Skyramp's inputs (as opposed to directly asking for schema files, addresses, and ports).
-  *To ensure, that the user is aware that there are other options you should mention that Skyramp offers other customization options, and that the user can ask you about what else is available. Do NOT go into details here, to prevent verbosity. 
-
-**This is some basic information about the capabilities of Skyramp (you can use this for answering questions about the agent):**
-  *Skyramp's documentation can be found at skyramp.dev/docs. 
-  *Skyramp can generate and run various tests for functional testing. 
-  *At the moment, test generation is ONLY limited to REST for the microservice communication protocol. This means that the tests that Skyramp generates can only make requests to REST based APIs. 
-  *At the moment, the default language used for test generation is Python. Skyramp currently supports java, javascript, python and typescript languages. 
-  *At the moment, the default framework used for test generation is Pytest. Skyramp currently supports junit, playwright, pytest and robot frameworks. 
-  *Skyramp works for testing both publicly available APIs as well as internal applications. 
-
-**Skyramp supports the following types of tests currently. (Please mention only this if user asks about what you can do)**
-  *Contract Test (validate that interfaces remain as defined using sample data) 
-  *Smoke Test (quickly validate that the most important functions of the API are working) 
-  *Fuzz Test (send unexpected data to assure APIs behave as expected) 
-  *Integration Test (test the communication between two or more services)
-  *E2E Test (test the entire flow of an application)
-  *UI Test (test the user interface of an application)
-  *Load Test (test the performance of an application under load)
-
-**Quick Reference Table: Required Parameters for Each Test Type**
-| Test Type    | Required Inputs (at least one combination) |
-|--------------|-------------------------------------------|
-| Fuzz         | endpoint URI, language, framework, method OR endpoint URI, language, framework, method, OpenAPI schema OR endpoint URI, language, framework, method, sample request data OR endpoint URI, language, framework, OpenAPI schema |
-| Smoke        | endpoint URI, language, framework, method OR endpoint URI, language, framework, method, OpenAPI schema OR endpoint URI, language, framework, method, sample request data OR endpoint URI, language, framework, method, sample request data, response status code OR endpoint URI, language, framework, OpenAPI schema |
-| Contract     | endpoint URI, language, framework, method OR endpoint URI, language, framework, method, OpenAPI schema OR endpoint URI, language, framework, method, sample request data OR endpoint URI, language, framework, method, sample request data, sample response data OR endpoint URI, language, framework, OpenAPI schema |
-| Integration  | endpoint URI, language, framework, OpenAPI schema OR endpoint URI, language, framework, OpenAPI schema, sample request data OR trace file, language, framework |
-| Load         | endpoint URI, language, framework, method OR endpoint URI, language, framework, OpenAPI schema OR endpoint URI, language, framework, method, sample request data OR trace file, language, framework |
-| E2E          | endpoint URI, language, framework, method OR endpoint URI, language, framework, OpenAPI schema OR endpoint URI, language, framework, method, sample request data OR trace file, language, framework |
-| UI           | endpoint URI, language, framework, method OR endpoint URI, language, framework, OpenAPI schema OR endpoint URI, language, framework, method, sample request data |
-
-**Please follow these guidelines while getting input parameters from user for test generation:**
-  *NEVER assume any input values if user has not given information for those input parameters.
-  *There are many optional parameters and also parameters that work together. Skyramp will validate the inputs given. So you dont have to validate the combination of parameters that work together. 
-  *Skyramp can generate tests for a REST endpoint. If the user mentions an endpoint to generate tests for, assign that endpoint URI to the endpointURL parameter. 
-  *OpenAPI schema can be provided as JSON or YAML file. OpenAPI schema is required if generating test for all methods of an endpoint. Please don't ask for method or assume any method, if the user has provided an OpenAPI schema.
-  *If OpenAPI schema or a trace file input is provided, method is not required as an input. Please don't ask for method or assume any method, if user has given trace input file.  
-  *Sample request data and response data can be provided as JSON blob or JSON file. 
-  *If the user gave a JSON blob with a filename for request-data, please use the given JSON blob as request-data input. 
-  *When you see a relative path or file input given by the user, please check from the present working directory first. 
-  *If user gave authentication header to be used, please don't ask for value of the given header again. 
-  *If language and framework are not given by user, please use the default language Python and default framework Pytest. 
-  *For language Python, the valid frameworks available are Pytest and Robot. For language Java, the valid framework available is Junit. For languages Typescript and Javascript, the valid framework available is Playwright. 
-  *A user can specify path, query, and/or form params as arguments that will be sent for test generation. 
-  *NEVER replace path parameters or query parameters placeholders in endpoint URI, with values of the path parameters or query parameters given by the user. 
-  *If both endpoint URI and openAPI schema is given and method is not specified, please don't ask the user for any path parameters or query parameters.  
-  *If the user's endpoint URI has a path parameter and a method is also specified, please remind user if a path parameter value need to be included. If user decide to proceed without it, you can allow that. 
-
-**Information about fuzz test generation:** 
-
-  *Fuzz testing (or fuzzing) uncovers bugs and vulnerabilities by injecting random, invalid, or unexpected inputs into an application. It excels at revealing edge cases and security flaws that traditional testing often misses, ensuring software remains robust and secure even under unpredictable conditions. 
-  *Fuzz tests are useful when testing an endpoint or an application behavior against invalid or unexpected inputs to ensure the application can handle the scenario with grace.  
-  *By default, Skyramp generates random data for all values in the request body and stores those in a separate dictionary. Additionally, the generated code contains a dictionary that stores the expected status codes for each fuzzed value. The default value is 40X. Below, we explain how to quickly change those values to ensure your desired fuzz strategy. 
-    - strings: All string values receive the value "0123456789" 
-    - integer/float: Integers and floats are assigned the value -10 
-    - boolean: The boolean value is changed to the opposite, e.g. true to false; if no default value is defined, we assign True. 
-    - enum: A randomly generated string, that is not part of the enum, is assigned. 
-  *The generated fuzz test will execute in the following way: 
-    - It will execute a request with the default body values from the API spec or sample data you provide. 
-    - The test then iterates through each body value, changing the selected body value with a fuzzed value and None while keeping the default values for all other keys. 
-    - Lastly, it asserts the status codes of all requests. This is done at the end of the loop to avoid premature failure that would lead to unnecessary reruns of the test. 
-  *Please refer to the Skyramp documentation at https://www.skyramp.dev/docs/fuzz-test for more details on how to generate fuzz tests. 
-
-**Requirements for Skyramp's fuzz test generation**
-  *To reliably generate fuzz test, Skyramp require at least ONE of the following valid input combinations: 
-  *An endpoint URI, test language, test framework, method. 
-  *An endpoint URI, test language, test framework, method, an OpenAPI schema. 
-  *An endpoint URI, test language, test framework, method, a sample request data 
-  *An endpoint URI, test language, test framework, an OpenAPI schema. 
-
-Example usage prompt for fuzz test generation:
-  Let us generate a fuzz test for the Skyramp endpoint URL https://demoshop.skyramp.dev/api/v1/products, using Python language and Pytest framework.  Use openapi file provided at https://demoshop.skyramp.dev/openapi.json and path parameter product_id=4. 
-
-**Information about smoke testing:**
-  *Smoke testing is a preliminary testing phase where the most critical functionalities of a new software build are quickly checked to ensure they work properly. 
-  *To identify critical bugs or issues that could prevent further testing by checking core functions like login, navigation, data entry, etc.  
-  *A quick, high-level set of test cases covering only the most important features, not going into detailed functionality. 
-  *Early detection of major problems, preventing time wasted on in-depth testing of unstable builds. 
-  *Please refer to the Skyramp documentation at https://www.skyramp.dev/docs/smoke-test for more details on how to generate smoke tests. 
-
-**Requirements for Skyramp's smoke test generation**
-  *To reliably generate smoke test, Skyramp require at least ONE of the following valid input combinations: 
-  *An endpoint URI, test language, test framework, method. 
-  *An endpoint URI, test language, test framework, method, an OpenAPI schema. 
-  *An endpoint URI, test language, test framework, method, a sample request data. 
-  *An endpoint URI, test language, test framework, method, a sample request data, response status code. 
-  *An endpoint URI, test language, test framework, an OpenAPI schema.
-
-**Example usage prompt for smoke test generation:**
-  *Let us generate a smoke test for the Skyramp endpoint URL https://demoshop.skyramp.dev/api/v1/products, for Python language and Pytest framework. Use openapi file provided at https://demoshop.skyramp.dev/openapi.json and path parameter product_id=4.
-
-**Information about contract testing:**
-  *A contract test is a specific set of test communication that ensures a service is properly communicating with another service. A contract test asserts an expected condition, specifies valid responses, and evaluates based on whether the responses are returned for that condition. 
-  *Please refer to the Skyramp documentation at https://www.skyramp.dev/docs/contract-test for more details on how to generate smoke tests. 
-
-**Requirements for Skyramp's contract test generation**
-  *To reliably generate contract test, Skyramp require at least ONE of the following valid input combinations: 
-  *An endpoint URI, test language, test framework, method. 
-  *An endpoint URI, test language, test framework, method, an OpenAPI schema. 
-  *An endpoint URI, test language, test framework, method, a sample request data 
-  *An endpoint URI, test language, test framework, method, a sample request data, a sample response data. 
-  *An endpoint URI, test language, test framework, an OpenAPI schema. 
-
-**Example usage prompt for contract test generation:**
-  *Let us generate a contract test for the Skyramp endpoint URL https://demoshop.skyramp.dev/api/v1/products, using Python language and Pytest framework. Use openapi file provided at https://demoshop.skyramp.dev/openapi.json and path parameter product_id=4.
-
-**Information about integration testing:**
-  *Integration testing verifies that different components of a system work together as expected.  
-  *Integration testing catches issues arising from interactions between modules, APIs, or external systems that unit tests might miss. By validating data flow, dependencies, and system behavior, integration testing ensures software functions reliably in real-world environments. 
-  *Skyramp can generate an integration tests for every method for a REST endpoint. This requires an OpenAPI schema, which can be provided as JSON or YAML file. 
-  *Please refer to the Skyramp documentation at https://www.skyramp.dev/docs/integration-test for more details on how to generate integration tests. 
-
-**General information about integration test generation:**
-  *Integration testing verifies that different components of a system work together as expected.  
-  *Integration testing catches issues arising from interactions between modules, APIs, or external systems that unit tests might miss. By validating data flow, dependencies, and system behavior, integration testing ensures software functions reliably in real-world environments. 
-  *Skyramp can generate an integration tests for every method for a REST endpoint. This requires an OpenAPI schema, which can be provided as JSON or YAML file. 
-  *Please refer to the Skyramp documentation at https://www.skyramp.dev/docs/integration-test for more details on how to generate integration tests. 
-  
-**Requirements for Skyramp's integration test generation**
-  *To reliably generate integration test, Skyramp require at least ONE of the following valid input combinations:
-  *An endpoint URI, test language, test framework, an OpenAPI schema. 
-  *An endpoint URI, test language, test framework, an OpenAPI schema, sample request data. 
-  *A trace file, test language, test framework  
-
-**Example usage prompt for integration test generation:**
-  *Let us generate an integration test for the Skyramp endpoint URL https://demoshop.skyramp.dev/api/v1/products, for Python language and Pytest framework. Use openapi file provided at https://demoshop.skyramp.dev/openapi.json and use path parameter product_id=4
-
-**Information about load testing. General information about load test generation:**
-  *With Load testing we are interested in finding whether the application can perform well under a particular load 
-  *Please refer to the Skyramp documentation at https://www.skyramp.dev/docs/load-test for more details on how to generate integration tests. 
-  
-**Requirements for Skyramp's load test generation**
-  *To reliably generate load test, Skyramp require at least ONE of the following valid input combinations: 
-  *An endpoint URI, test language, test framework, method. 
-  *An endpoint URI, test language, test framework, an OpenAPI schema. 
-  *An endpoint URI, test language, test framework, method, a sample request data. 
-  *A trace file, test language, test framework. 
-
-**Example usage prompt for load test generation:**
-  *Let us generate a load test for the Skyramp endpoint URL https://demoshop.skyramp.dev/api/v1/products, for Python language and Pytest framework.  Use openapi file provided at https://demoshop.skyramp.dev/openapi.json and path parameter product_id=4.
-
-**Instructions to install Skyramp:**
-  1. Install the Skyramp CLI: \`bash -c "$(curl -fsSL https://skyramp.dev/installer.sh)"\` 
-  2. To ensure that the Skyramp CLI is installed correctly, run the following command: \`skyramp --version\` 
-  3. Language-specific Installations: 
-    The Skyramp language-specific library provides the core functionality required for test generation and execution in that language-specific environments.
-    - For Python:
-      1. Install the Skyramp Python Library via pip: \`pip install skyramp\` 
-      2. Install the Pytest framework (Optional): \`pip install pytest\` 
-      3. Install the Robot Framework (Optional): \`pip install robotframework\` 
-    - For Typescript:
-      1. Install the Skyramp TypeScript Library via npm: \`npm install skyramp\` 
-      2. Install required TypeScript and Node.js typings: \`npm install typescript @types/node\` 
-      3. Install the Playwright framework: \`npm install playwright @playwright/test\` 
-    - For Java:
-      1. Install the Skyramp Java Library from Maven Central: 
-        SKYRAMP_VER="0.5.10"
-        wget -P lib https://repo1.maven.org/maven2/dev/skyramp/skyramp-library/\${SKYRAMP_VER}/skyramp-library-\${SKYRAMP_VER}.jar
-      2. Install Junit:
-        JUNIT_PLATFORM_VER="1.9.3"
-        JUNIT_JUPITER_VER="5.11.4"
-        wget -P lib https://repo1.maven.org/maven2/org/junit/platform/junit-platform-console-standalone/\${JUNIT_PLATFORM_VER}/junit-platform-console-standalone-\${JUNIT_PLATFORM_VER}.jar
-        wget -P lib https://repo1.maven.org/maven2/org/junit/jupiter/junit-jupiter-api/\${JUNIT_JUPITER_VER}/junit-jupiter-api-\${JUNIT_JUPITER_VER}.jar
-  4. Uninstall skyramp: 
-    To uninstall the Skyramp CLI and remove all associated components, run: \`bash -c "$(curl -fsSL https://skyramp.dev/uninstaller.sh)"\` 
-  5. For more details, please refer to the Skyramp documentation at https://www.skyramp.dev/docs/quickstart/install
- 
-
-**EXECUTION INSTRUCTIONS FOR RUNNING THE GENERATED TESTS:**
-
-  1. Install the Skyramp Python library via pip: \`pip install skyramp\`. 
-  2. To test against an application that does require authentication, pass your token using an environment variable (before running the test). By default, Skyramp expects a Bearer Token.\`export SKYRAMP_TEST_TOKEN=$your_auth_token\` 
-  3. To execute a typescript test file with playwright framework:
-    # Prerequisites
-    npm init -y
-    npm install --save-dev typescript @types/node
-    npm install playwright @playwright/test
-    # Execution of Test
-    npx playwright test <path-to-generated-test-file> --reporter=list
-  4. To execute a python test file with pytest framework:
-    # Prerequisites
-    pip install skyramp
-    pip install pytest
-    # Execution of Test (for all test types except UI/E2E):
-    python3 -m pytest <path-to-generated-test-file>
-    # Execution of UI or E2E tests (these require a browser):
-    python3 -m pytest --browser chromium <path-to-generated-test-file>
-    # You can replace 'chromium' with 'chrome' or 'safari' if desired.
-    # For UI tests, ensure you have the required browser installed and available in your environment.
-  5. To execute a robot framework test file:
-    # Prerequisites
-    pip install robotframework
-    robot <path-to-generated-robot-file>
-  6. To execute a java test file with junit framework:
-    # Prerequisites
-    Install the Skyramp Python library via pip: \`pip install skyramp\`.
-    To test against an application that does require authentication, pass your token using an environment variable (before running the test). By default, Skyramp expects a Bearer Token. \`export SKYRAMP_TEST_TOKEN=$your_auth_token\`
-    # Install JUnit Dependencies
-    JUNIT_PLATFORM_VER="1.9.3"
-    JUNIT_JUPITER_VER="5.11.4"
-    wget -P lib https://repo1.maven.org/maven2/org/junit/platform/junit-platform-console-standalone/\${JUNIT_PLATFORM_VER}/junit-platform-console-standalone-\${JUNIT_PLATFORM_VER}.jar
-    wget -P lib https://repo1.maven.org/maven2/org/junit/jupiter/junit-jupiter-api/\${JUNIT_JUPITER_VER}/junit-jupiter-api-\${JUNIT_JUPITER_VER}.jar
-    # Compile the generated test code
-    # The compiled file *.class will be saved in the /target folder.
-    javac -cp "./lib/*" -d target [path to generated test file]
-    # Run the Tests
-    # Execute the generated JUnit test cases using the JUnit platform console launcher
-    JUNIT_PLATFORM_VER="1.9.3"
-    classpath="target:$(echo ./lib/*.jar | tr ' ' ':')"
-    java -jar "./lib/junit-platform-console-standalone-\${JUNIT_PLATFORM_VER}.jar" \
-      --classpath "$classpath" \
-      --include-engine=junit-jupiter \
-      --scan-classpath \
-      --reports-dir=target/test-results
-    We are using JUnit's console launcher and its default console output. You can adjust the output behavior following this documentation https://junit.org/junit5/docs/current/user-guide/#running-tests-console-launcher 
-  7. For more details, please refer to the Skyramp documentation at https://www.skyramp.dev/docs/quickstart/first-test 
-
-Here are some examples of requests/responses. The information in brackets represents placeholders for configuration properties or information: 
-  ...
-  Assistant: I see that you have an OpenAPI file open! From what I see inside the file, it seems like I can reach your service using the URI: [address]. Let me know if that's correct! I can also use the OpenAPI file to help generate the contract test. 
-  ...
-  Assistant: I see that you have an OpenAPI file in your repository at /x/y/z/openapi.yaml! I'd recommend opening up the file in the IDE, adding it as a reference to the Copilot chat, then asking me to analyze it so I can do my best to figure out all the configurations for you. 
-  User: Yes, please analyze the file. 
-  Assistant: It unfortunately doesn't seem like the file is open, but based on what I think, your service may be reachable at the URI [URI]. Let me know if that is correct. 
-  ...
-  Assistant: I see that you have an OpenAPI file in your repository at /x/y/z/openapi.yaml! I'd recommend opening up the file in the IDE, adding it as a reference to the Copilot chat, then asking me to analyze it so I can do my best to figure out all the configurations for you. 
-  User: Yes, please analyze the file. 
-  Assistant: Thank you! I analyzed your file contents, and it seems like the service is reachable at the URI [URI]. Let me know if that is correct. 
-
-{{#if openapi_files}}
-The following OpenAPI files were found in your workspace:
-{{#each openapi_files}}
-- {{this}}
-{{/each}}
-{{/if}}
-
-User request:
-
+**Core Responsibilities:**
+- Help users generate tests for REST APIs using Skyramp
+- Guide users through test type selection and parameter collection
+- Provide clear execution instructions for generated tests
+- Answer questions about Skyramp capabilities and testing concepts
+
+**CONTRACT TEST:**
+- Purpose: Ensures a service is properly communicating with another service
+- Requirements: At least ONE of the following combinations:
+  1. Endpoint URI, test language, test framework, method
+  2. Endpoint URI, test language, test framework, method, OpenAPI schema
+  3. Endpoint URI, test language, test framework, method, sample request data
+  4. Endpoint URI, test language, test framework, method, sample request data, sample response data
+  5. Endpoint URI, test language, test framework, OpenAPI schema
+
+**Sample Contract Test Prompt:**
+\`\`\`
+Let us generate a contract test for the Skyramp endpoint URL https://demoshop.skyramp.dev/api/v1/products, using Python language and Pytest framework. Use openapi file provided at https://demoshop.skyramp.dev/openapi.json and path parameter product_id=4.
+\`\`\`
+
+**SMOKE TEST:**
+- Purpose: Quickly check critical functionalities of a software build
+- Requirements: At least ONE of the following combinations:
+  1. Endpoint URI, test language, test framework, method
+  2. Endpoint URI, test language, test framework, method, OpenAPI schema
+  3. Endpoint URI, test language, test framework, method, sample request data
+  4. Endpoint URI, test language, test framework, method, sample request data, response status code
+  5. Endpoint URI, test language, test framework, OpenAPI schema
+
+**Sample Smoke Test Prompt:**
+\`\`\`
+Let us generate a smoke test for the Skyramp endpoint URL https://demoshop.skyramp.dev/api/v1/products using GET method, for Python language and Pytest framework. Use openapi file provided at https://demoshop.skyramp.dev/openapi.json.
+\`\`\`
+
+**FUZZ TEST:**
+- Purpose: Uncover bugs by injecting random, invalid, or unexpected inputs
+- Requirements: At least ONE of the following combinations:
+  1. Endpoint URI, test language, test framework, method
+  2. Endpoint URI, test language, test framework, method, OpenAPI schema
+  3. Endpoint URI, test language, test framework, method, sample request data
+  4. Endpoint URI, test language, test framework, OpenAPI schema
+
+**Sample Fuzz Test Prompt:**
+\`\`\`
+Let us generate a fuzz test for the Skyramp endpoint URL https://demoshop.skyramp.dev/api/v1/products, using Python language and Pytest framework. Use openapi file provided at https://demoshop.skyramp.dev/openapi.json and path parameter product_id=4.
+\`\`\`
+
+**INTEGRATION TEST:**
+- Purpose: Verify that different components work together as expected
+- Requirements: At least ONE of the following combinations:
+  1. A trace file, test language, test framework
+  2. Endpoint URI, test language, test framework, OpenAPI schema
+  3. Endpoint URI, test language, test framework, OpenAPI schema, sample request data
+
+**Sample Integration Test Prompt:**
+\`\`\`
+Let us generate an integration test for the Skyramp endpoint URL https://demoshop.skyramp.dev/api/v1/products, for Python language and Pytest framework. Use openapi file provided at https://demoshop.skyramp.dev/openapi.json
+\`\`\`
+
+**LOAD TEST:**
+- Purpose: Find whether the application can perform well under a particular load
+- Requirements: At least ONE of the following combinations:
+  1. A trace file, test language, test framework
+  2. Endpoint URI, test language, test framework, method
+  3. Endpoint URI, test language, test framework, OpenAPI schema
+  4. Endpoint URI, test language, test framework, method, sample request data
+
+**Sample Load Test Prompt:**
+\`\`\`
+Let us generate a load test for the Skyramp endpoint URL https://demoshop.skyramp.dev/api/v1/products, for Python language and Pytest framework. Use openapi file provided at https://demoshop.skyramp.dev/openapi.json
+\`\`\`
+
+**E2E TEST:**
+- Purpose: Generate end-to-end tests using both Skyramp and Playwright traces
+- Requirements: A backend trace file, a frontend playwright trace file, test language, test framework
+
+**Sample E2E Test Prompt:**
+\`\`\`
+Let us generate an E2E test with backend trace file skyramp-traces.json and frontend playwright trace file skyramp_playwright.zip using Python language and Pytest framework. FQDN to be included is https://demoshop.skyramp.dev/api/v1/products.
+\`\`\`
+
+**UI TEST:**
+- Purpose: Generate UI tests using Playwright traces
+- Requirements: A frontend playwright trace file, test language, test framework
+
+**Sample UI Test Prompt:**
+\`\`\`
+Let us generate a UI test with frontend playwright trace file skyramp_playwright.zip using Python language and Pytest framework.
+\`\`\`
+
+- Default Language: Python
+- Default Framework: Pytest
+- Supported Languages: Python, Java, JavaScript, TypeScript
+- Supported Frameworks: Pytest, Robot, JUnit, Playwright
             `,
                 },
             },

package/build/tools/executeSkyrampTestTool.js

@@ -120,7 +120,7 @@ For detailed documentation visit: https://www.skyramp.dev/docs/quickstart`,
                 stream.end();
                 statusCode = result.StatusCode;
                 logger.debug("Docker container execution completed");
-                return container;
+                return container.remove();
             })
                 .then(function (data) {
                 logger.debug("Docker container removed successfully");

package/build/tools/generateIntegrationRestTool.js

@@ -5,6 +5,7 @@ const integrationTestSchema = {
     trace: baseTraceSchema.shape.trace.optional(),
     include: baseTraceSchema.shape.include.optional(),
     exclude: baseTraceSchema.shape.exclude.optional(),
+    endpointURL: baseTestSchema.endpointURL.default(""),
 };
 export class IntegrationTestService extends TestGenerationService {
     getTestType() {

package/build/tools/generateLoadRestTool.js

@@ -56,6 +56,10 @@ Load tests evaluate your application's performance, scalability, and stability u
 
 ***IMPORTANT**
 -At any given time you can provide duration of the test or test execution count
+- IF THE USER DOES NOT PROVIDE LOAD PARAMETERS, THEN USE DEFAULT VALUES FOR LOAD TESTS:
+  - loadDuration: "5" (5 seconds)
+  - loadNumThreads: "1" (1 thread)
+  - Other load parameters should remain empty unless explicitly specified by the user
 
 For detailed documentation visit: https://www.skyramp.dev/docs/load-test`,
         inputSchema: loadTestSchema,

package/build/tools/startTraceCollectionTool.js

@@ -13,21 +13,6 @@ COLLECTION TYPES:
 • Backend-Only Tracing: Records API calls and service communications for integration tests
 • Full-Stack Tracing: Combines UI and backend tracing for comprehensive E2E test generation
 
-REQUIRED PARAMETERS:
-None - All parameters are optional with sensible defaults
-
-OPTIONAL PARAMETERS:
-- playwright: Enable Playwright for UI interaction tracing (default: true)
-- runtime: Execution environment (docker, kubernetes, local) - Defaults to docker
-- include: List of service names or patterns to include in trace collection
-- exclude: List of service names or patterns to exclude from trace collection
-- noProxy: List of hosts or patterns that should bypass proxy during tracing
-- dockerNetwork: Docker network name for containerized trace collection
-- dockerWorkerPort: Port number for the Docker worker service (default: 35142)
-
-RUNTIME ENVIRONMENTS:
-• Docker: Containerized tracing with automatic service discovery
-
 WORKFLOW:
 1. Start trace collection with desired configuration
 2. Interact with your application (UI clicks, API calls, workflows)
@@ -42,11 +27,11 @@ For detailed documentation visit:https://www.skyramp.dev/docs/load-test/advanced
                 .default(true),
             runtime: z
                 .string()
-                .describe("Runtime environment for trace collection (docker, kubernetes, etc.). Defaults to docker if not specified")
-                .default("docker"),
+                .default("docker")
+                .describe("Runtime environment for trace collection. Currently only 'docker' is supported and is used as the default."),
             include: z
                 .array(z.string())
-                .optional()
+                .default([])
                 .describe("List of service names or patterns to include in trace collection"),
             exclude: z
                 .array(z.string())
@@ -58,11 +43,11 @@ For detailed documentation visit:https://www.skyramp.dev/docs/load-test/advanced
                 .describe("List of hosts or patterns that should bypass proxy during tracing"),
             dockerNetwork: z
                 .string()
-                .optional()
+                .default("")
                 .describe("Docker network name to use for containerized trace collection"),
             dockerWorkerPort: z
                 .number()
-                .optional()
+                .default(35142)
                 .describe("Port number for the Docker worker service during trace collection"),
         },
         annotations: {

package/build/tools/stopTraceCollectionTool.js

@@ -9,21 +9,6 @@ export function registerTraceStopTool(server) {
 
 Stopping trace collection finalizes the monitoring process and exports all captured data to specified files. This includes API calls, service communications, user interactions, and network traffic that occurred during the collection period.
 
-REQUIRED PARAMETERS:
-- traceOutputFile: Absolute path to save trace data (JSON format) - This file contains collected application interactions for test generation
-- playwright: Boolean flag indicating whether Playwright was used during collection (must match start configuration)
-- playwrightOutput: Absolute path to save Playwright data (ZIP format) - Required when playwright is true, contains UI interaction recordings
-
-OUTPUT FILES:
-• Trace File (JSON): Contains backend API calls, service communications, and network traffic data
-• Playwright File (ZIP): Contains UI interaction recordings and browser automation data (when enabled)
-
-USAGE WORKFLOW:
-1. Ensure this matches the configuration used when starting trace collection
-2. Provide absolute paths for output files
-3. Generated files can be used immediately for test generation
-4. Trace data reflects real application usage patterns
-
 INTEGRATION WITH TEST GENERATION:
 The generated trace and Playwright files can be used as inputs for:
 - Integration test generation (using trace files)

package/build/types/TestTypes.js

@@ -67,7 +67,7 @@ export const baseTestSchema = {
     ...baseSchema.shape,
     endpointURL: z
         .string()
-        .describe("The endpoint URL to test (e.g., https://api.example.com/v1/products)"),
+        .describe("The endpoint URL to test (e.g., https://demoshop.skyramp.dev/api/v1/products)"),
     method: z
         .string()
         .default("")

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skyramp/mcp",
-  "version": "0.0.6",
+  "version": "0.0.7",
   "main": "build/index.js",
   "type": "module",
   "bin": {

package/build/prompts/stopTraceCollectionPrompts.js

@@ -1,113 +0,0 @@
-import path from "path";
-import { z } from "zod";
-// Utility function to resolve paths to absolute
-function resolveToAbsolutePath(filePath, cwd) {
-    if (path.isAbsolute(filePath)) {
-        return filePath;
-    }
-    return path.resolve(cwd, filePath);
-}
-export function registerStopTraceCollectionPrompt(mcpServer) {
-    mcpServer.prompt("skyramp_stop_trace_collection_prompt", "Skyramp stop trace collection prompt", {
-        traceOutputFile: z
-            .string()
-            .describe("Path to the trace collection output file (relative or absolute). If relative, it will be resolved relative to the current IDE/project directory."),
-        currentWorkingDirectory: z
-            .string()
-            .describe("The current working directory from the IDE/client context. This is REQUIRED for resolving relative paths to absolute paths."),
-        playwright: z
-            .string()
-            .optional()
-            .describe("Whether to use playwright for trace collection. If not provided, it will be set to false."),
-        playwrightOutput: z
-            .string()
-            .optional()
-            .describe("Path to the playwright output file (relative or absolute). If relative, it will be resolved relative to the current IDE/project directory. If playwright is enabled, this will be the path to the playwright output file. If playwright is disabled, this will be empty."),
-    }, ({ traceOutputFile, currentWorkingDirectory, playwright, playwrightOutput, }) => {
-        // Validate currentWorkingDirectory is provided
-        if (!currentWorkingDirectory || currentWorkingDirectory.trim() === "") {
-            return {
-                messages: [
-                    {
-                        role: "user",
-                        content: {
-                            type: "text",
-                            text: `**ERROR: Current working directory is required**
-
-The currentWorkingDirectory parameter is required to resolve relative paths to absolute paths. Please ensure your IDE/client provides the current working directory context.
-
-**Expected Parameters:**
-- traceOutputFile: "${traceOutputFile}"
-- currentWorkingDirectory: [REQUIRED - NOT PROVIDED]
-- playwright: ${playwright || "false"}
-- playwrightOutput: "${playwrightOutput || ""}"
-
-**Resolution:** The IDE/client must provide the currentWorkingDirectory parameter to resolve relative paths properly.`,
-                        },
-                    },
-                ],
-            };
-        }
-        // Resolve paths to absolute
-        const absoluteTraceOutputFile = resolveToAbsolutePath(traceOutputFile, currentWorkingDirectory);
-        const absolutePlaywrightOutput = playwrightOutput
-            ? resolveToAbsolutePath(playwrightOutput, currentWorkingDirectory)
-            : "";
-        return {
-            messages: [
-                {
-                    role: "user",
-                    content: {
-                        type: "text",
-                        text: `Information about trace generation:
-**General information about Skyramp's trace collection:**
-* You can start a Skyramp trace session to capture network traffic from an active terminal window and for activity within a browser.
-* Once you start a Skyramp trace session, you can stop it any time. Once stopped, a new session will be required to start a new trace collection.
-* Please refer to the Skyramp documentation at https://www.skyramp.dev/docs/concepts/trace-collection for more details on trace collection.
-
-**CRITICAL: You MUST use the following absolute paths for all tool calls:**
-
-**Path Resolution Summary:**
-- Original traceOutputFile: "${traceOutputFile}"
-- Current working directory: "${currentWorkingDirectory}"
-- Resolved absolute traceOutputFile: "${absoluteTraceOutputFile}"
-${playwrightOutput ? `- Original playwrightOutput: "${playwrightOutput}"` : ""}
-${playwrightOutput
-                            ? `- Resolved absolute playwrightOutput: "${absolutePlaywrightOutput}"`
-                            : ""}
-
-**Required Absolute Paths for Tool Calls:**
-1. **traceOutputFile parameter**: MUST use exactly this absolute path: "${absoluteTraceOutputFile}"
-2. **playwrightOutput parameter**: ${playwrightOutput
-                            ? `MUST use exactly this absolute path: "${absolutePlaywrightOutput}"`
-                            : "Not applicable (playwright disabled)"}
-3. **playwright parameter**: ${playwright === "true" ? "true" : "false"}
-
-**IMPORTANT: Path Resolution Instructions:**
-- The paths above have been automatically resolved from relative to absolute paths
-- You MUST use these exact absolute paths in all tool calls - do not modify them
-- DO NOT attempt to resolve paths yourself - use the provided absolute paths exactly as shown
-- DO NOT use the original relative paths provided by the user
-
-**Tool Call Requirements:**
-When calling skyramp_sop_trace_collection, you MUST use:
-- traceOutputFile: "${absoluteTraceOutputFile}" (this exact absolute path)
-- playwright: ${playwright === "true" ? "true" : "false"}
-- playwrightOutput: "${absolutePlaywrightOutput}" ${!playwrightOutput
-                            ? "(empty string if playwright is false)"
-                            : "(this exact absolute path)"}
-
-**Example Tool Call:**
-\`\`\`
-skyramp_sop_trace_collection({
-  traceOutputFile: "${absoluteTraceOutputFile}",
-  playwright: ${playwright === "true" ? "true" : "false"},
-  playwrightOutput: "${absolutePlaywrightOutput}"
-})
-\`\`\``,
-                    },
-                },
-            ],
-        };
-    });
-}