Skip to main content
Glama
run-as-root

Warden Magento MCP Server

by run-as-root

warden_stop_project

Stop a Warden-managed Magento 2 development environment to halt services and free system resources. Provide the project directory path to execute this action.

Instructions

Stop a Warden project environment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_pathYesPath to the project directory

Implementation Reference

  • The handler function that executes the tool logic: extracts project_path from arguments and calls executeWardenCommand with 'warden env down' to stop the Warden project environment.
    async stopProject(args) {
      const { project_path } = args;
      return await this.executeWardenCommand(
        project_path,
        ["env", "down"],
        "Stopping Warden project environment",
      );
    }
  • Input schema definition for the warden_stop_project tool, requiring project_path.
    inputSchema: {
      type: "object",
      properties: {
        project_path: {
          type: "string",
          description: "Path to the project directory",
        },
      },
      required: ["project_path"],
    },
  • server.js:325-326 (registration)
    Registration in the CallToolRequestSchema switch statement that dispatches calls to the stopProject handler.
    case "warden_stop_project":
      return await this.stopProject(request.params.arguments);
  • server.js:58-71 (registration)
    Tool registration in the ListToolsRequestSchema response, including name, description, and schema.
    {
      name: "warden_stop_project",
      description: "Stop a Warden project environment",
      inputSchema: {
        type: "object",
        properties: {
          project_path: {
            type: "string",
            description: "Path to the project directory",
          },
        },
        required: ["project_path"],
      },
    },
  • Helper function used by stopProject to execute the warden command, handle errors, and format the response.
    async executeWardenCommand(project_path, wardenArgs, description) {
      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(
          "warden",
          wardenArgs,
          absoluteProjectPath,
        );
    
        const commandStr = `warden ${wardenArgs.join(" ")}`;
        const isSuccess = result.code === 0;
    
        return {
          content: [
            {
              type: "text",
              text: `${description} ${isSuccess ? "completed successfully" : "failed"}!\n\nCommand: ${commandStr}\nWorking directory: ${absoluteProjectPath}\nExit Code: ${result.code}\n\nOutput:\n${result.stdout || "(no output)"}\n\nErrors:\n${result.stderr || "(no errors)"}`,
            },
          ],
          isError: !isSuccess,
        };
      } catch (error) {
        const commandStr = `warden ${wardenArgs.join(" ")}`;
        return {
          content: [
            {
              type: "text",
              text: `Failed to execute command:\n\nCommand: ${commandStr}\nWorking directory: ${absoluteProjectPath}\nError: ${error.message}\n\nOutput:\n${error.stdout || "(no output)"}\n\nErrors:\n${error.stderr || "(no errors)"}`,
            },
          ],
          isError: true,
        };
      }
    }
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 states the action ('Stop') but doesn't explain what 'stop' entails (e.g., whether it halts containers, shuts down services, or destroys data), potential side effects, permissions required, or error conditions. This leaves significant gaps for a mutation tool.

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, direct sentence with zero wasted words. It's front-loaded with the core action and target, making it highly efficient and easy to parse.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It lacks details on behavior, side effects, success/failure indicators, and how it relates to sibling tools. The agent would need to guess about the tool's impact and proper use.

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 schema description coverage is 100%, with the single parameter 'project_path' well-documented in the schema. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline for high schema coverage without compensating value.

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 ('Stop') and target ('a Warden project environment'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'warden_stop_svc' (which stops services rather than projects), but the specificity of 'project environment' provides some implicit distinction.

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. It doesn't mention prerequisites (e.g., the project must be running), contrast with 'warden_stop_svc', or indicate when not to use it. The agent must infer usage from the tool name and context alone.

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/run-as-root/warden-mcp-server'

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