Skip to main content
Glama
Sign In
Impreza Host MCP Server

Impreza Host MCP Server

by imprezahost
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

impreza_vps_list_backups

View all available backups for a Proxmox VPS. Provide the service ID to retrieve backup ID, timestamp, and size.

Instructions

List the available backups for a Proxmox VPS (id, timestamp, size). Read-only.

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_list_backups"
  }
}

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

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It states read-only behavior, which is helpful, but lacks details on error cases, empty results, or authentication requirements.

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 a single sentence plus 'Read-only.', no unnecessary words. Essential information 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 simple list tool with one parameter and no output schema, the description adequately covers functionality, input source, and return fields. Minor omission: no mention of pagination or limit, but not critical.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The parameter service_id is already described in the schema (100% coverage). The description adds value by specifying it is numeric and referencing impreza_list_services, providing context beyond the schema.

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 tool lists backups for a Proxmox VPS, specifying fields (id, timestamp, size) and marks as read-only. It distinguishes from sibling tools like impreza_vps_create_backup.

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?

Description implies usage with a service_id from impreza_list_services, but does not explicitly state when to use vs alternatives or provide exclusion criteria.

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