Skip to main content
Glama
hostinger

hostinger-api-mcp

Official

VPS_stopProjectV1

Gracefully stop all services in a Docker Compose project by shutting down containers in reverse dependency order. Preserve container configurations and data volumes for temporary halts without loss.

Instructions

Stops all running services in a Docker Compose project while preserving container configurations and data volumes.

This operation gracefully shuts down containers in reverse dependency order.

Use this to temporarily halt a project without removing data or configurations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectNameYesDocker Compose project name using alphanumeric characters, dashes, and underscores only
virtualMachineIdYesVirtual Machine ID

Implementation Reference

  • Schema definition for the 'VPS_stopProjectV1' tool, describing its purpose to stop Docker Compose project services on a VPS, with input parameters virtualMachineId (number) and projectName (string), and generic response.
       * Stops all running services in a Docker Compose project while preserving container configurations and data volumes. 
    
    This operation gracefully shuts down containers in reverse dependency order. 
    
    Use this to temporarily halt a project without removing data or configurations.
       */
      "VPS_stopProjectV1": {
        params: {
          /**
           * Virtual Machine ID
           */
          virtualMachineId: number;
          /**
           * Docker Compose project name using alphanumeric characters, dashes, and underscores only
           */
          projectName: string;
        };
        response: any; // Response structure will depend on the API
      };
Behavior4/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. It effectively describes key behavioral traits: the graceful shutdown process ('gracefully shuts down containers in reverse dependency order'), data preservation ('preserving container configurations and data volumes'), and the temporary nature of the operation ('temporarily halt'). It doesn't mention permissions, rate limits, or error conditions, but covers the core operational behavior well.

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 perfectly structured with three focused sentences: the core purpose, behavioral detail, and usage guidance. Each sentence earns its place with no wasted words, and the most important information (what the tool does) is front-loaded.

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

Completeness4/5

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

For a mutation tool with no annotations and no output schema, the description does well by explaining the operation's behavior, data preservation, and temporary nature. It could be more complete by mentioning what happens to network connections, whether the operation is synchronous/asynchronous, or what the response contains, but it covers the essential context given the tool's complexity.

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 already fully documents both parameters (projectName and virtualMachineId). The description doesn't add any parameter-specific information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 ('Stops all running services'), target resource ('in a Docker Compose project'), and scope ('while preserving container configurations and data volumes'). It distinguishes from sibling tools like VPS_deleteProjectV1 (which removes data) and VPS_restartProjectV1 (which restarts rather than stops).

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 ('Use this to temporarily halt a project without removing data or configurations'), which implicitly differentiates it from destructive alternatives. However, it doesn't explicitly name when NOT to use it or mention specific sibling alternatives like VPS_deleteProjectV1 or VPS_startProjectV1.

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