Skip to main content
Glama

List APT repositories

proxmox_list_node_repositories
Read-only

Lists a Proxmox node's APT repository files with enabled state, URIs, suites, components, parse warnings, and configured standard repos; use the path/index and digest to update them.

Instructions

List a node's APT repositories by file with enabled/disabled state, URIs, suites and components, any parse errors and warnings (e.g. enterprise repo without subscription, mixed suites), and which standard Proxmox repositories are configured. Use path/index and the digest with proxmox_set_node_repository.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "proxmox_list_node_repositories"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full unprocessed objects from the API (larger)
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, but the description adds substantive behavior: results are grouped by file, and it surfaces parse errors and warnings such as an enterprise repo without a subscription or mixed suites. That warning disclosure is genuinely useful context not available in the annotations, though it says nothing about error handling or result size behavior beyond the schema's 'raw' note.

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?

Two sentences, front-loaded with the core action and return contents, followed by a short workflow pointer. The first sentence is dense but every clause names a distinct returned field or warning type, so it earns its length.

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?

With no output schema, the description appropriately enumerates what is returned (per-file repos, states, URIs, suites, components, warnings, standard repo flags). Combined with 100% schema coverage on inputs, an agent has enough to call it correctly; only error/failure behavior is unaddressed, a minor gap for a read-only tool.

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%, with both 'raw' and 'node' documented including the PROXMOX_DEFAULT_NODE fallback, so the schema carries the parameter burden. The description's mention of 'path/index' and 'digest' refers to output fields rather than input parameters and adds no input-side meaning, so baseline 3 applies.

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?

States a specific verb and resource ('List a node's APT repositories by file') and enumerates the scope precisely: enabled/disabled state, URIs, suites, components, parse errors, warnings, and standard Proxmox repo presence. An agent can distinguish this from sibling listing tools like proxmox_list_node_updates or proxmox_list_node_services without inspecting the schema.

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 routes the agent to the companion mutation tool: 'Use path/index and the digest with proxmox_set_node_repository,' establishing the read-before-write workflow. It does not state explicit when-not-to-use conditions, but the read-only enumeration context is clear enough to select it correctly.

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