Skip to main content
Glama
run-as-root

Warden Magento MCP Server

by run-as-root

warden_start_svc

Start Warden system services for Magento 2 development environments by providing the project directory path to manage local development workflows.

Instructions

Start Warden system services

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_pathYesPath to the project directory

Implementation Reference

  • The main handler function for the 'warden_start_svc' tool. It extracts the project_path from arguments and executes 'warden svc up' command in the project directory using the shared executeWardenCommand helper.
    async startSvc(args) {
      const { project_path } = args;
      return await this.executeWardenCommand(
        project_path,
        ["svc", "up"],
        "Starting Warden system services",
      );
    }
  • Input schema definition for the 'warden_start_svc' tool, specifying that project_path is a required string parameter.
    {
      name: "warden_start_svc",
      description: "Start Warden system services",
      inputSchema: {
        type: "object",
        properties: {
          project_path: {
            type: "string",
            description: "Path to the project directory",
          },
        },
        required: ["project_path"],
      },
    },
  • server.js:327-328 (registration)
    Registration/dispatch in the CallToolRequestSchema handler switch statement, routing calls to the startSvc method.
    case "warden_start_svc":
      return await this.startSvc(request.params.arguments);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Start' implies a state-changing operation, but the description doesn't reveal what permissions are needed, whether the operation is reversible, what happens if services are already running, or what side effects might occur. This is a significant gap 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, efficient sentence with zero wasted words. It's appropriately sized for a simple tool and gets straight to the point without unnecessary elaboration.

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 doesn't explain what 'starting services' entails, what happens on success/failure, or how this differs from related tools. The context signals show this is a single-parameter tool, but the description doesn't provide enough operational context.

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 has 100% description coverage, so the parameter 'project_path' is documented in the schema. The description adds no additional parameter semantics beyond what's already in the structured data, which meets the baseline expectation when schema coverage is complete.

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 ('Start') and target resource ('Warden system services'), which provides a specific verb+resource combination. However, it doesn't distinguish this tool from its sibling 'warden_start_project', leaving some ambiguity about scope.

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 like 'warden_start_project' or 'warden_stop_svc'. There's no mention of prerequisites, dependencies, or appropriate contexts for invocation.

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