Skip to main content
Glama
hostinger

hostinger-api-mcp

Official

VPS_installMonarxV1

Install Monarx malware scanner on a virtual machine to detect and prevent malicious software. Use this endpoint on Hostinger MCP server to enable malware protection for VPS instances.

Instructions

Install the Monarx malware scanner on a specified virtual machine.

Monarx is a security tool designed to detect and prevent malware infections on virtual machines. By installing Monarx, users can enhance the security of their virtual machines, ensuring that they are protected against malicious software.

Use this endpoint to enable malware protection on VPS instances.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
virtualMachineIdYesVirtual Machine ID

Implementation Reference

  • TypeScript interface definition (schema) for the 'VPS_installMonarxV1' tool, specifying the input parameter 'virtualMachineId' (number) and generic response.
    "VPS_installMonarxV1": {
      params: {
        /**
         * Virtual Machine ID
         */
        virtualMachineId: number;
      };
      response: any; // Response structure will depend on the API
    };
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions that Monarx 'detects and prevents malware infections' and 'enhances security,' but it lacks critical details: whether this requires specific permissions, if it's a one-time or ongoing process, potential impacts on VM performance, installation time, or error handling. For a mutation tool (installation implies a change) with zero annotation coverage, this is a significant gap.

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 appropriately sized and front-loaded: the first sentence clearly states the purpose. The subsequent sentences provide context about Monarx and its benefits, which are useful but could be more concise. There's minimal waste, though the link to Monarx might be extraneous if the agent doesn't need it.

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 complexity (a mutation tool installing security software), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like permissions, side effects, or response format. While it explains what Monarx is, it misses operational details needed for safe and effective use by an AI agent.

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 (the parameter 'virtualMachineId' is described as 'Virtual Machine ID'), so the schema does the heavy lifting. The description adds no additional parameter semantics beyond what's in the schema—it doesn't explain format, constraints, or examples. With high schema coverage, the baseline is 3, and the description doesn't compensate with extra 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 tool's purpose: 'Install the Monarx malware scanner on a specified virtual machine.' It uses a specific verb ('Install') and resource ('Monarx malware scanner'), and mentions the target ('virtual machine'). However, it doesn't explicitly differentiate from its sibling tool 'VPS_uninstallMonarxV1' beyond the obvious install/uninstall distinction, which is why it doesn't reach a perfect score.

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 minimal usage guidance. It states 'Use this endpoint to enable malware protection on VPS instances,' which implies a context of enhancing security, but it doesn't specify when to use this tool versus alternatives (e.g., other security tools or methods), prerequisites, or exclusions. No explicit alternatives or when-not-to-use scenarios are mentioned.

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

Related 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