Skip to main content
Glama
Sign In
Impreza Host MCP Server

Impreza Host MCP Server

by imprezahost
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

impreza_vps_create_backup

Trigger an on-demand backup of a Proxmox VPS by service ID. Poll backup list to confirm completion.

Instructions

Trigger an on-demand backup of a Proxmox VPS. Poll impreza_vps_list_backups for completion.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "service_id": "<service_id>"
    },
    "name": "impreza_vps_create_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
service_idYesVPS service id (numeric; from impreza_list_services).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so the description must cover behavior. It reveals the async nature by instructing polling, but omits side effects, permissions, or limits on concurrent backups.

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. Front-loaded with the core action, followed by a critical next step. Every word earns its place.

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?

Given its simplicity (one param, no output schema), the description covers the essential action and polling guidance. Minor missing context: concurrent backup handling or typical duration.

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% with a clear parameter description. The tool description adds no extra value to the parameter beyond what the schema already provides.

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 explicitly states the action ('Trigger an on-demand backup') and the resource ('Proxmox VPS'), distinguishing it from sibling tools like power or list_backups.

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 description implies to poll for completion using a sibling tool, but does not specify when to use this tool versus alternatives (e.g., scheduled backups) or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools