Skip to main content
Glama
dockergiant

RollDev MCP Server

by dockergiant

rolldev_stop_project

Stop a RollDev project environment to halt running services and free up resources. Provide the project directory path to safely terminate the environment.

Instructions

Stop a RollDev project environment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_pathYesPath to the project directory

Implementation Reference

  • The stopProject() method is the handler for the 'rolldev_stop_project' tool. It extracts project_path from args and calls executeRollCommand with ['env', 'down'] to stop the RollDev project environment.
    async stopProject(args) {
      const { project_path } = args;
      return await this.executeRollCommand(
        project_path,
        ["env", "down"],
        "Stopping RollDev project environment",
      );
    }
  • The tool registration with its input schema. Defines the 'rolldev_stop_project' tool requiring a single 'project_path' string parameter.
    {
      name: "rolldev_stop_project",
      description: "Stop a RollDev project environment",
      inputSchema: {
        type: "object",
        properties: {
          project_path: {
            type: "string",
            description: "Path to the project directory",
          },
        },
        required: ["project_path"],
      },
    },
  • server.js:299-300 (registration)
    The case branch in the CallToolRequestSchema handler that dispatches 'rolldev_stop_project' to the stopProject method.
    case "rolldev_stop_project":
      return await this.stopProject(request.params.arguments);
  • The executeRollCommand() helper method used by stopProject to actually run the 'roll env down' shell command in the project directory.
      async executeRollCommand(project_path, rollArgs, description, timeoutMs = 300000, saveToFile = false) {
        if (!project_path) {
          throw new Error("project_path is required");
        }
    
        const normalizedProjectPath = project_path.replace(/\/+$/, "");
        const absoluteProjectPath = resolve(normalizedProjectPath);
    
        if (!existsSync(absoluteProjectPath)) {
          throw new Error(
            `Project directory does not exist: ${absoluteProjectPath}`,
          );
        }
    
        try {
          const result = await this.executeCommand(
            "roll",
            rollArgs,
            absoluteProjectPath,
            timeoutMs,
          );
    
          const commandStr = `roll ${rollArgs.join(" ")}`;
          const isSuccess = result.code === 0;
    
          // Save output to file only when explicitly requested
          const logFilePath = saveToFile
            ? this.saveOutputToFile(result.stdout, result.stderr, commandStr, absoluteProjectPath)
            : null;
    
          let responseText;
          if (logFilePath) {
            // Output saved to file
            const outputPreview = (result.stdout || "").substring(0, 500);
            const stderrPreview = (result.stderr || "").substring(0, 500);
            responseText = `${description} ${isSuccess ? "completed successfully" : "failed"}!
    
    Command: ${commandStr}
    Working directory: ${absoluteProjectPath}
    Exit Code: ${result.code}${result.timedOut ? " (TIMED OUT)" : ""}
    
    📁 Full output saved to file:
    ${logFilePath}
    
    Output Preview (first 500 chars):
    ${outputPreview || "(no output)"}${(result.stdout || "").length > 500 ? "\n...(truncated)" : ""}
    
    Errors Preview (first 500 chars):
    ${stderrPreview || "(no errors)"}${(result.stderr || "").length > 500 ? "\n...(truncated)" : ""}`;
          } else {
            // Return inline output
            responseText = `${description} ${isSuccess ? "completed successfully" : "failed"}!
    
    Command: ${commandStr}
    Working directory: ${absoluteProjectPath}
    Exit Code: ${result.code}${result.timedOut ? " (TIMED OUT)" : ""}
    
    Output:
    ${result.stdout || "(no output)"}
    
    Errors:
    ${result.stderr || "(no errors)"}`;
          }
    
          return {
            content: [
              {
                type: "text",
                text: responseText,
              },
            ],
            isError: !isSuccess,
          };
        } catch (error) {
          const commandStr = `roll ${rollArgs.join(" ")}`;
    
          // Save error output to file only when explicitly requested
          const logFilePath = saveToFile
            ? this.saveOutputToFile(error.stdout, error.stderr, commandStr, absoluteProjectPath)
            : null;
    
          let responseText;
          if (logFilePath) {
            responseText = `Failed to execute command:
    
    Command: ${commandStr}
    Working directory: ${absoluteProjectPath}
    Error: ${error.message}
    
    📁 Full output saved to file:
    ${logFilePath}`;
          } else {
            responseText = `Failed to execute command:
    
    Command: ${commandStr}
    Working directory: ${absoluteProjectPath}
    Error: ${error.message}
    
    Output:
    ${error.stdout || "(no output)"}
    
    Errors:
    ${error.stderr || "(no errors)"}`;
          }
    
          return {
            content: [
              {
                type: "text",
                text: responseText,
              },
            ],
            isError: true,
          };
        }
      }
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It merely says 'stop' without explaining what stopping entails (e.g., kills processes, preserves state, is reversible). This leaves ambiguity for the agent.

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 a single, concise sentence with no extraneous words. However, it is so minimal that it may not fully serve its purpose; conciseness should not sacrifice essential information.

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 tool has only one parameter and no output schema, the description could still provide more context about the stopping process or effects. It lacks completeness for an agent to understand the full impact.

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 (project_path described as 'Path to the project directory'). The description adds no further semantics beyond what the schema already provides, so baseline applies.

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 action ('Stop') and the resource ('a RollDev project environment'). It distinguishes from sibling tools like rolldev_start_project and rolldev_stop_svc by specifying 'project environment' rather than service or other component.

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?

No guidance on when to use this tool versus alternatives (e.g., stop_svc). It does not specify prerequisites, such as the project being running, or when not to use (e.g., if the project is already stopped).

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/dockergiant/rolldev-mcp-server'

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