Skip to main content
Glama

end_codegen_session

Terminate a code generation session and create the corresponding test file by providing the session ID, streamlining browser automation workflows within the Playwright MCP Server.

Instructions

End a code generation session and generate the test file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesID of the session to end

Implementation Reference

  • Primary implementation of the end_codegen_session tool, defining the Tool object with name, description, parameters schema, and the async handler function that processes the session, generates the Playwright test file using PlaywrightGenerator, writes it to disk, cleans up browser resources, and returns the result.
    export const endCodegenSession: Tool = {
      name: 'end_codegen_session',
      description: 'End the current code generation session and generate Playwright test',
      parameters: {
        type: 'object',
        properties: {
          sessionId: {
            type: 'string',
            description: 'ID of the session to end'
          }
        },
        required: ['sessionId']
      },
      handler: async ({ sessionId }: { sessionId: string }) => {
        try {
          const recorder = ActionRecorder.getInstance();
          const session = recorder.endSession(sessionId);
    
          if (!session) {
            throw new Error(`Session ${sessionId} not found`);
          }
    
          if (!session.options) {
            throw new Error(`Session ${sessionId} has no options configured`);
          }
    
          const generator = new PlaywrightGenerator(session.options);
          const result = await generator.generateTest(session);
    
          // Double check output directory exists
          const outputDir = path.dirname(result.filePath);
          await fs.mkdir(outputDir, { recursive: true });
          
          // Write test file
          try {
            await fs.writeFile(result.filePath, result.testCode, 'utf-8');
          } catch (writeError: any) {
            throw new Error(`Failed to write test file: ${writeError.message}`);
          }
    
          // Close Playwright browser and cleanup
          try {
            if (global.browser?.isConnected()) {
              await global.browser.close();
            }
          } catch (browserError: any) {
            console.warn('Failed to close browser:', browserError.message);
          } finally {
            global.browser = undefined;
            global.page = undefined;
          }
    
          const absolutePath = path.resolve(result.filePath);
    
          return {
            filePath: absolutePath,
            outputDirectory: outputDir,
            testCode: result.testCode,
            message: `Generated test file at: ${absolutePath}\nOutput directory: ${outputDir}`
          };
        } catch (error: any) {
          // Ensure browser cleanup even on error
          try {
            if (global.browser?.isConnected()) {
              await global.browser.close();
            }
          } catch {
            // Ignore cleanup errors
          } finally {
            global.browser = undefined;
            global.page = undefined;
          }
          
          throw new Error(`Failed to end codegen session: ${error.message}`);
        }
      }
  • Input schema definition for the end_codegen_session tool, used in createToolDefinitions() for MCP tool registration.
    {
      name: "end_codegen_session",
      description: "End a code generation session and generate the test file",
      inputSchema: {
        type: "object",
        properties: {
          sessionId: { 
            type: "string", 
            description: "ID of the session to end" 
          }
        },
        required: ["sessionId"]
      }
  • Registration and dispatch logic in the main handleToolCall function, importing and routing end_codegen_session calls to its handler via switch statement.
    switch (name) {
      case 'start_codegen_session':
        return await handleCodegenResult(startCodegenSession.handler(args));
      case 'end_codegen_session':
        return await handleCodegenResult(endCodegenSession.handler(args));
      case 'get_codegen_session':
        return await handleCodegenResult(getCodegenSession.handler(args));
      case 'clear_codegen_session':
        return await handleCodegenResult(clearCodegenSession.handler(args));
    }
  • Import statement bringing endCodegenSession Tool into the main tool handler.
    import { 
      startCodegenSession,
      endCodegenSession,
      getCodegenSession,
      clearCodegenSession
    } from './tools/codegen/index.js';
  • Export of codegenTools array including endCodegenSession for use by other modules.
    export const codegenTools = [
      startCodegenSession,
      endCodegenSession,
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that ending a session 'generate[s] the test file', which implies a write or output operation, but doesn't specify if this is destructive, requires specific permissions, or details the format or location of the generated file. This leaves significant gaps in understanding the tool's behavior.

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?

The description is a single, efficient sentence that front-loads the key action and outcome without any wasted words. It is appropriately sized for the tool's complexity, earning a top score for conciseness.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'generate the test file' entails—such as the file format, location, or any side effects—leaving the agent with insufficient context for a mutation tool that produces output.

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?

The input schema has 100% description coverage, with 'sessionId' clearly documented as 'ID of the session to end'. The description adds no additional parameter semantics beyond this, so it meets the baseline of 3 for adequate but not enhanced parameter information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('End a code generation session') and the outcome ('generate the test file'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'clear_codegen_session' or 'get_codegen_session', which prevents a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, such as 'clear_codegen_session' or 'start_codegen_session', nor does it mention any prerequisites or context for usage. This lack of explicit when/when-not instructions limits its helpfulness.

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

Related 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/BhanuTJ93/MCP'

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