Skip to main content
Glama

OS templates

list_os_templates
Read-onlyIdempotent

Retrieve available OS templates for rebuilding a specific server by providing its server ID, so you can choose the correct image before initiating a rebuild.

Instructions

List the OS templates available for a rebuild.

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": {
      "serverId": "<serverId>"
    },
    "name": "list_os_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdYesServer ID (UUID) from list_servers

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered without the description. The description adds only the 'for a rebuild' scoping context; it says nothing about result size, filtering, or whether templates are server-specific, so it clears the lowered bar but does not enrich it much.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

One short sentence, front-loaded with the verb and resource, with zero filler. It is arguably too terse rather than padded, so it earns a 4 rather than a 5 on completeness of framing.

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 single-parameter read-only list tool with rich annotations and full schema coverage, the description covers what the tool returns at a high level and why it is called. Missing details—such as whether results are scoped to the given server or how many entries come back—are minor given the absence of an output schema.

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?

There is a single required parameter (serverId) with 100% schema description coverage, including a UUID hint and a pointer to list_servers. The description adds no meaning beyond the schema, so the baseline 3 for fully documented parameters applies.

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?

States a specific verb ('List') and resource ('OS templates'), plus a scoping qualifier ('available for a rebuild') that hints at the operational context. It is distinguishable from siblings like list_isos or list_resource_packs by resource name alone, though the description never explicitly contrasts them.

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 phrase 'available for a rebuild' implies the tool is used when preparing a server rebuild, which is useful contextual guidance. However, it gives no explicit when/when-not rules and does not name any alternative (e.g., list_isos) for different template types, leaving the agent to infer the boundary.

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