Skip to main content
Glama
hostinger

hostinger-api-mcp

Official

VPS_getTemplateDetailsV1

Fetch detailed specifications of a virtual machine OS template using its ID to ensure informed decisions before deployment on Hostinger’s infrastructure.

Instructions

Retrieve detailed information about a specific OS template for virtual machines.

Use this endpoint to view specific template specifications before deployment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
templateIdYesTemplate ID

Implementation Reference

  • Schema definition including description, input parameters (templateId: number), and response type for the VPS_getTemplateDetailsV1 tool.
      /**
       * Retrieve detailed information about a specific OS template for virtual machines.
    
    Use this endpoint to view specific template specifications before deployment.
       */
      "VPS_getTemplateDetailsV1": {
        params: {
          /**
           * Template ID
           */
          templateId: 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 full burden. It states this is a retrieval operation, implying read-only behavior, but doesn't disclose any behavioral traits like authentication requirements, rate limits, error conditions, or what 'detailed information' includes. For a tool 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero waste. The first sentence states the core purpose, and the second provides usage context. It's appropriately sized and front-loaded with essential information.

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?

Given the tool's low complexity (1 parameter, 100% schema coverage) but no annotations and no output schema, the description is minimally adequate. It covers purpose and basic usage but lacks behavioral details and output information, leaving gaps for an AI agent to operate effectively.

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 the single parameter 'templateId' documented in the schema as 'Template ID'. The description adds no additional parameter semantics beyond implying it's for a 'specific OS template'. Baseline 3 is appropriate when the schema does the heavy lifting.

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 'retrieve' and resource 'detailed information about a specific OS template for virtual machines', making the purpose unambiguous. However, it doesn't explicitly differentiate from its sibling 'VPS_getTemplatesV1' (which likely lists templates rather than providing details for a specific one), missing 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 Guidelines3/5

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

The second sentence provides implied usage context ('view specific template specifications before deployment'), suggesting when to use it. However, it lacks explicit guidance on when not to use it or alternatives (e.g., vs. 'VPS_getTemplatesV1' for listing), and no prerequisites 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