Skip to main content
Glama
elgentos

Magento 2 Development MCP Server

by elgentos

Module Observer List

dev-module-observer-list

List all Magento 2 module observers to identify event handlers and their configurations. Filter by specific events to analyze observer behavior and dependencies in your development environment.

Instructions

List all Magento 2 module observers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventNoFilter by specific event name
formatNoOutput formattable

Implementation Reference

  • The handler function that constructs and executes the magerun2 dev:module:observer:list command, handles JSON parsing if needed, and returns formatted output or error.
    async ({ format = "table", event }) => {
      let command = `magerun2 dev:module:observer:list --format=${format}`;
    
      if (event) {
        command += ` "${event}"`;
      }
    
      const result = await executeMagerun2Command(command, format === "json");
    
      if (!result.success) {
        return {
          content: [{
            type: "text",
            text: result.error
          }],
          isError: true
        };
      }
    
      const responseText = format === "json"
        ? `Observer list (${format} format):\n\n${JSON.stringify(result.data, null, 2)}`
        : `Observer list (${format} format):\n\n${result.data}`;
    
      return {
        content: [{
          type: "text",
          text: responseText
        }]
      };
    }
  • Zod input schema for the tool, defining output format and optional event filter.
    inputSchema: {
      format: z.enum(["table", "json", "csv"])
        .default("table")
        .describe("Output format"),
      event: z.string()
        .optional()
        .describe("Filter by specific event name")
    }
  • src/index.ts:438-482 (registration)
    MCP server tool registration call for 'dev-module-observer-list', including title, description, schema, and inline handler.
    server.registerTool(
      "dev-module-observer-list",
      {
        title: "Module Observer List",
        description: "List all Magento 2 module observers",
        inputSchema: {
          format: z.enum(["table", "json", "csv"])
            .default("table")
            .describe("Output format"),
          event: z.string()
            .optional()
            .describe("Filter by specific event name")
        }
      },
      async ({ format = "table", event }) => {
        let command = `magerun2 dev:module:observer:list --format=${format}`;
    
        if (event) {
          command += ` "${event}"`;
        }
    
        const result = await executeMagerun2Command(command, format === "json");
    
        if (!result.success) {
          return {
            content: [{
              type: "text",
              text: result.error
            }],
            isError: true
          };
        }
    
        const responseText = format === "json"
          ? `Observer list (${format} format):\n\n${JSON.stringify(result.data, null, 2)}`
          : `Observer list (${format} format):\n\n${result.data}`;
    
        return {
          content: [{
            type: "text",
            text: responseText
          }]
        };
      }
    );
  • Shared helper function for executing magerun2 CLI commands with timeout, JSON parsing option, Magento-specific error detection, and consistent response format.
    async function executeMagerun2Command(command: string, parseJson: boolean = false): Promise<{
      success: true;
      data: any;
      rawOutput: string;
    } | {
      success: false;
      error: string;
      isError: true;
    }> {
      try {
        const { stdout, stderr } = await execAsync(command, {
          cwd: process.cwd(),
          timeout: 30000 // 30 second timeout
        });
    
        if (stderr && stderr.trim()) {
          console.error("magerun2 stderr:", stderr);
        }
    
        if (parseJson) {
          try {
            return { success: true, data: JSON.parse(stdout), rawOutput: stdout };
          } catch (parseError) {
            return {
              success: false,
              error: `Error parsing magerun2 JSON output: ${parseError}\n\nRaw output:\n${stdout}`,
              isError: true
            };
          }
        }
    
        return { success: true, data: stdout.trim(), rawOutput: stdout };
    
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
    
        // Check if magerun2 is not found
        if (errorMessage.includes("command not found") || errorMessage.includes("not recognized")) {
          return {
            success: false,
            error: "Error: magerun2 command not found. Please ensure n98-magerun2 is installed and available in your PATH.\n\nInstallation instructions: https://github.com/netz98/n98-magerun2",
            isError: true
          };
        }
    
        // Check if not in Magento directory
        if (errorMessage.includes("not a Magento installation") || errorMessage.includes("app/etc/env.php")) {
          return {
            success: false,
            error: "Error: Current directory does not appear to be a Magento 2 installation. Please run this command from your Magento 2 root directory.",
            isError: true
          };
        }
    
        return {
          success: false,
          error: `Error executing magerun2 command: ${errorMessage}`,
          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 but only states the action without details on permissions, rate limits, output behavior, or side effects. It lacks information on what 'list' entails (e.g., pagination, default sorting), making it insufficient for a tool with no annotation coverage.

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 no wasted words, making it highly concise and front-loaded. It efficiently communicates the core purpose 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?

Given the tool's listing function, no output schema, and lack of annotations, the description is incomplete. It does not address return values, error handling, or behavioral traits, leaving gaps that could hinder an AI agent's ability to use it effectively in context with sibling tools.

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?

Schema description coverage is 100%, so the schema fully documents both parameters ('event' and 'format'). The description adds no additional parameter semantics beyond what the schema provides, such as examples or usage context, meeting the baseline for high coverage.

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 verb ('List') and resource ('all Magento 2 module observers'), making the purpose immediately understandable. However, it does not explicitly differentiate from sibling tools like 'dev-module-list' or 'sys-cron-list', which also list resources but different types, so it misses full sibling 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, such as how it differs from 'dev-module-list' or other listing tools in the sibling set. There is no mention of context, prerequisites, or exclusions, leaving usage unclear.

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/elgentos/magento2-dev-mcp'

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