Skip to main content
Glama
hostinger

hostinger-api-mcp

Official

VPS_uninstallMonarxV1

Uninstalls the Monarx malware scanner from a specified VPS instance. If Monarx is not installed, the request has no effect.

Instructions

Uninstall the Monarx malware scanner on a specified virtual machine.

If Monarx is not installed, the request will still be processed without any effect.

Use this endpoint to remove malware scanner from VPS instances.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
virtualMachineIdYesVirtual Machine ID

Implementation Reference

  • Schema definition for VPS_uninstallMonarxV1 tool - defines it as a DELETE request to /api/vps/v1/virtual-machines/{virtualMachineId}/monarx with virtualMachineId as the required integer input parameter.
    {
      "name": "VPS_uninstallMonarxV1",
      "description": "Uninstall the Monarx malware scanner on a specified virtual machine.\n\nIf Monarx is not installed, the request will still be processed without any effect.\n\nUse this endpoint to remove malware scanner from VPS instances.",
      "method": "DELETE",
      "path": "/api/vps/v1/virtual-machines/{virtualMachineId}/monarx",
      "inputSchema": {
        "type": "object",
        "properties": {
          "virtualMachineId": {
            "type": "integer",
            "description": "Virtual Machine ID"
          }
        },
        "required": [
          "virtualMachineId"
        ]
      },
      "security": [
        {
          "apiToken": []
        }
      ],
      "group": "vps"
    },
  • Tool list export containing VPS_uninstallMonarxV1 along with all other VPS tools - this array is exported and imported by the VPS server entry point.
    ];
    export default tools;
  • The generic API handler executeApiCall in the MCPServer class handles all non-custom tools including VPS_uninstallMonarxV1. Since VPS_uninstallMonarxV1 has no 'custom' flag, it is executed via this method which makes a DELETE request to /api/vps/v1/virtual-machines/{virtualMachineId}/monarx, substituting {virtualMachineId} from the input parameters.
    async executeApiCall(tool, params) {
      // Get method and path from tool
      const method = tool.method;
      let path = tool.path;
    
      // Clone params to avoid modifying the original
      const requestParams = { ...params };
    
      // Replace path parameters with values from params
      Object.entries(requestParams).forEach(([key, value]) => {
        const placeholder = `{${key}}`;
        if (path.includes(placeholder)) {
          path = path.replace(placeholder, encodeURIComponent(String(value)));
          delete requestParams[key]; // Remove used parameter
        }
      });
    
      // Build the full URL
      const baseUrl = this.baseUrl.endsWith("/") ? this.baseUrl : `${this.baseUrl}/`;
      const cleanPath = path.startsWith("/") ? path.slice(1) : path;
      const url = new URL(cleanPath, baseUrl).toString();
    
      this.log('debug', `API Request: ${method} ${url}`);
    
      try {
        // Configure the request
        const config = {
          method: method.toLowerCase(),
          url,
          headers: { ...this.headers },
          timeout: 60000, // 60s
          validateStatus: function (status) {
            return status < 500; // Resolve only if the status code is less than 500
          }
        };
      
        const bearerToken = process.env['API_TOKEN'] || process.env['APITOKEN']; // APITOKEN for backwards compatibility
        if (bearerToken) {
          config.headers['Authorization'] = `Bearer ${bearerToken}`;
        } else {
          this.log('error', `Bearer Token environment variable not found: API_TOKEN`);
        }
    
        // Add parameters based on request method
        if (["GET", "DELETE"].includes(method)) {
          // For GET/DELETE, send params as query string
          config.params = { ...(config.params || {}), ...requestParams };
        } else {
          // For POST/PUT/PATCH, send params as JSON body
          config.data = requestParams;
          config.headers["Content-Type"] = "application/json";
        }
    
        this.log('debug', "Request config:", {
          url: config.url,
          method: config.method,
          params: config.params,
          headers: Object.keys(config.headers)
        });
    
        // Execute the request
        const response = await axios(config);
        this.log('debug', `Response status: ${response.status}`);
    
        return response.data;
    
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        this.log('error', `API request failed: ${errorMessage}`);
    
        if (axios.isAxiosError(error)) {
          const responseData = error.response?.data;
          const responseStatus = error.response?.status;
    
          this.log('error', 'API Error Details:', {
            status: responseStatus,
            data: typeof responseData === 'object' ? JSON.stringify(responseData) : responseData
          });
    
          // Rethrow with more context for better error handling
          const detailedError = new Error(`API request failed with status ${responseStatus}: ${errorMessage}`);
          detailedError.response = error.response;
          throw detailedError;
        }
    
        throw error;
      }
    }
  • The CallToolRequestSchema handler in MCPServer.setupHandlers() dispatches tool calls. For VPS_uninstallMonarxV1 (which is not marked as 'custom'), it routes to executeApiCall, constructing and sending the API request.
    this.server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { id, name, arguments: params } = request.params;
      this.log('debug', "Handling CallTool request", { id, name, params });
    
      let toolName;
      let toolDetails;
    
      // Find the requested tool
      for (const [tid, tool] of this.tools.entries()) {
        if (tool.name === name) {
          toolName = name;
          break;
        }
      }
    
      if (!toolName) {
        throw new Error(`Tool not found: ${name}`);
      }
    
      toolDetails = this.toolList.find(t => t.name === toolName);
      if (!toolDetails) {
        throw new Error(`Tool details not found for ID: ${toolName}`);
      }
    
      try {
        this.log('info', `Executing tool: ${toolName}`);
    
        let result;
    
        if (toolDetails.custom) {
          result = await this.executeCustomTool(toolDetails, params || {});
        } else {
          result = await this.executeApiCall(toolDetails, params || {});
        }
    
        // Return the result in the correct MCP format
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(result)
            }
          ]
        };
    
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        const response = error.response;
        this.log('error', `Error executing tool ${name}: ${errorMessage}`);
    
        throw error;
      }
    });
Behavior3/5

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

With no annotations, the description bears full burden. It discloses idempotency (no effect if not installed), which is good. However, it does not mention other traits like destructiveness, required VM state, or consequences on related data. Partially transparent but gaps remain.

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?

Three sentences with the main purpose first. The third sentence is somewhat redundant ('remove malware scanner' reiterates). Still, it's short and front-loaded, earning a 4.

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

Completeness3/5

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

For a tool with one parameter and no output schema, the description provides the core action and idempotency. However, it lacks details on the response, potential errors, or side effects. Adequate for a simple tool but not fully complete.

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 coverage is 100% for the single parameter, so baseline is 3. The description adds no extra meaning beyond 'Virtual Machine ID'; it doesn't explain how to obtain or use it. No additional value.

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 tool uninstalls Monarx on a VM. It uses a specific verb ('Uninstall') and resource ('Monarx malware scanner') and distinguishes from the sibling VPS_installMonarxV1 by being the removal counterpart.

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

Usage Guidelines4/5

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

The description notes idempotency: if Monarx is not installed, the request processes without effect. This provides context on when it's safe to call. However, it does not explicitly state prerequisites or when to avoid using it, though the sibling tool implies the alternative.

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/hostinger/api-mcp-server'

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