Skip to main content
Glama

pve_storage_download

Download an ISO or CT template from a URL to a storage, with dry-run planning and optional verification using checksum.

Instructions

MUTATION: download an ISO (content=iso) or CT template (content=vztmpl) from a URL into a storage. Dry-run by default; confirm=True. Async — returns a UPID (poll with pve_task_status). The URL and its content are operator-trusted — Proximo does not verify or sandbox what it fetches. Use pve_storage_content to see what's already on a storage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesSource URL to download the ISO or CT template from.
nodeNoPVE node hosting the storage. Omit to use the configured default node.
confirmNoLeave `false` (default) to get a dry-run PLAN; set `true` to execute the download.
contentYesContent type of the downloaded file: `iso` or `vztmpl`.
storageYesStorage backend name to download the file into.
checksumNoExpected checksum of the downloaded file, used to verify integrity.
filenameYesFilename to save the downloaded content as on the storage.
proximo_targetNoWhich configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call.
checksum_algorithmNoAlgorithm the checksum was computed with (e.g. `sha256`). Required if checksum is given.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so description carries full burden. It discloses mutation, dry-run default, async nature, UPID return, and that the URL/content are operator-trusted without verification. This is comprehensive.

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?

Three sentences, front-loaded with core action, then dry-run/async behavior, then trust note and sibling reference. No wasted words, every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers core action, safety (dry-run), async behavior, trust implications, and references relevant sibling tool. Output schema exists, so return values not needed. Complete for this tool's 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%, so baseline 3 is appropriate. Description adds no extra param insight beyond schema (e.g., mentions URL, content, filename but schema already does). No need for compensation.

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 downloads an ISO (content=iso) or CT template (content=vztmpl) from a URL into a storage. It specifies the action, resource types, and distinguishes from siblings like pve_storage_content.

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?

Description mentions dry-run by default and async behavior, and references pve_storage_content to check existing content. This provides usage context, though it doesn't explicitly state when not to use the tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/john-broadway/proximo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server