Skip to main content
Glama
hostinger

hostinger-api-mcp

Official

VPS_getScanMetricsV1

Retrieve detailed scan metrics from the Monarx malware scanner for a specified virtual machine. Monitor malware scan results, detected threats, and security status to evaluate protection effectiveness.

Instructions

Retrieve scan metrics for the Monarx malware scanner installed on a specified virtual machine.

The scan metrics provide detailed information about malware scans performed by Monarx, including number of scans, detected threats, and other relevant statistics. This information is useful for monitoring security status of the virtual machine and assessing effectiveness of the malware scanner.

Use this endpoint to monitor VPS security scan results and threat detection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
virtualMachineIdYesVirtual Machine ID

Implementation Reference

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

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

No annotations are provided, so the description carries full burden. It correctly implies this is a read operation ('Retrieve'), but doesn't disclose behavioral traits like authentication requirements, rate limits, error conditions, or response format. The description adds useful context about what the metrics include, but lacks operational details.

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 with three focused paragraphs. The first sentence clearly states the purpose, subsequent sentences add useful context, and the final sentence reinforces usage. There's minimal redundancy, though the third paragraph slightly repeats monitoring concepts from the second.

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 single-parameter read tool with no annotations and no output schema, the description provides adequate purpose and usage context but lacks details about response format, error handling, or authentication requirements. It's complete enough for basic understanding but leaves operational gaps.

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% with one parameter clearly documented. The description adds context that the virtualMachineId parameter specifies 'a specified virtual machine' with Monarx installed, but doesn't provide additional semantics beyond what the schema already states. Baseline 3 is appropriate when schema does the heavy lifting.

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 specific action ('Retrieve scan metrics'), resource ('for the Monarx malware scanner installed on a specified virtual machine'), and scope ('detailed information about malware scans'). It distinguishes from siblings like VPS_getMetricsV1 by specifying Monarx scanner metrics rather than general metrics.

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 provides clear context for when to use this tool ('monitoring security status' and 'assessing effectiveness of the malware scanner'), and the last sentence reinforces this ('Use this endpoint to monitor VPS security scan results and threat detection'). However, it doesn't explicitly mention when not to use it or name specific alternatives among siblings.

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