Skip to main content
Glama
Sign In
Impreza Host MCP Server

Impreza Host MCP Server

by imprezahost
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

impreza_vps_list_templates

Retrieve available OS templates for a Proxmox VPS, providing IDs and labels to select a template for reinstallation.

Instructions

List the OS templates available for reinstalling a Proxmox VPS (template_id + label). Use to pick a template_id for impreza_vps_reinstall. 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_templates"
  }
}

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.2/5.0
Behavior4/5

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

Declares read-only operation and describes output (template_id + label). With no annotations, the description carries the burden; it adequately conveys safety and purpose without contradiction.

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, front-loaded with purpose, no redundant words. Every sentence adds value.

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 provides enough context: purpose, output fields, connection to reinstall, and read-only nature. Could mention error handling but not necessary for this 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 coverage is 100%, and the parameter description in the schema is sufficient. The tool description adds no new parameter-level information, so baseline score of 3 is appropriate.

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 it lists OS templates for VPS reinstallation, specifying output fields (template_id + label) and connecting to a sibling tool (impreza_vps_reinstall). This distinguishes it from other tools.

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?

Explicitly says use it to pick a template_id for impreza_vps_reinstall, and declares read-only. It doesn't provide exclusions or alternatives, but the context is clear enough for this simple list tool.

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