Skip to main content
Glama
bacarrdy

VPSnet

by bacarrdy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Extract service file archive

extract_service_file_archive

Extract zip, tar, tar.gz/tgz, or .gz archives on a VPSnet Firecracker server into a new destination path; skips links and special files for safe guest-side unpacking.

Instructions

Firecracker only: extract a zip, tar, tar.gz/tgz or single .gz archive with the guest agent's own reader into a destination that must not exist (default: next to the archive, without the archive extension). Only regular files and directories are written; links, devices and FIFOs are skipped, owners ignored, setuid/setgid/sticky masked; at most 100,000 entries and min(10 GiB, 90 % of free space). Always an operation this tool follows for waitSeconds (default 60). Needs agent capability services.guest-files-extract-v1 (agent_update_required otherwise; Cloud VPS: unsupported_service_type). Requires files:manage on a FULL-access API key as an explicit grant; the hosted connector needs vm:files:write. Execution-equivalent targets (authorized_keys, cron, systemd units, sudoers, PAM, profile files) are refused to every API key (filesExecEquivalentScopeMissing). Availability: Firecracker servers need the updated guest agent (filesUnavailable reason agent_update_required; node_update_required while the host node is not updated yet) and Cloud VPS (KVM) servers need the VDS file-manager switch (reason feature_disabled while it is off); relay any unavailable reason verbatim and never work around it. A server whose 2FA lock is on answers 423.

Input Schema

NameRequiredDescriptionDefault
archiveYesAbsolute path inside the server (UTF-8, at most 4096 bytes, no . or .. components)
orderNoYesTenant-owned service order number, e.g. VP12345
destinationNoAbsolute path inside the server (UTF-8, at most 4096 bytes, no . or .. components)
waitSecondsNoHow long this tool waits for a slow guest's operation before returning its operationId (default 30, recursive delete and extract 60)
confirmSystemPathNoSet true only after the user explicitly approved changing this operating-system path (otherwise 409 filesSystemPathConfirmRequired)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.3.17

TDQS

A4.6/5.0
Behavior5/5

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

Goes far beyond the annotations: it discloses that only regular files/dirs are written, special files are skipped, owners ignored and setuid/setgid/sticky masked, plus hard limits (100,000 entries, min(10 GiB, 90% free space)) and the non-overwrite constraint. It also enumerates authorization requirements, refused execution-equivalent paths, verbatim unavailable reasons, and the 423 2FA-lock response.

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?

Dense but front-loaded: the core action and its central constraint occupy the first sentence, with limits, permissions, and error codes following. It is long and packed with semicolon-separated clauses, but nearly every clause carries actionable information.

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 everything an agent needs despite there being no output schema: behavior on special files, limits, prerequisites, authorization scopes, platform availability reasons, and the returned operationId for slow operations. Nothing material is left to inference.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: the destination default ('next to the archive, without the archive extension'), the extract-specific waitSeconds default of 60 (vs the schema's generic 30), and the 409 filesSystemPathConfirmRequired tied to confirmSystemPath.

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 first sentence states a specific verb+resource (extract a zip/tar/tar.gz/.gz archive) and scopes it precisely ('Firecracker only', destination must not exist). An agent can distinguish this from siblings like upload_service_file or read_service_file without opening any 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?

Gives clear platform conditions for use: Firecracker servers need an updated guest agent, Cloud VPS (KVM) needs the VDS file-manager switch, and the required capability and permission grants are named. It does not, however, route the agent away to any alternative sibling tool when those conditions fail, so it stops short of full alternative guidance.

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