Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

linux_package_manager_commands

Read-onlyIdempotent

Cross-translate package manager commands across 9 Linux ecosystems. Select an operation to get the equivalent install, remove, update, or search command for each distro.

Instructions

Package Manager Commands. Look up and cross-translate a package-manager command across 9 Linux/Unix ecosystems (apt, dnf, pacman, apk, zypper, pkg, brew, snap, flatpak, nix). It BUILDS command strings from a static table — it never runs a package manager, installs, removes, or touches the host. The "operation" field selects the mode: "translate" renders one action (install, remove, update, search) for each target manager from the optional package list and from/to managers; "crossReferenceTable" returns the full action-by-manager command matrix; "packageNameMap" returns canonical-to-per-distro package-name aliases (e.g. apache2 vs httpd); "presets" returns ready-made example requests. Use this for distro-specific package commands; use linux_command_builder for general find/grep/rsync/tar one-liners and linux_bash_script_generator for full scripts. Returns the equivalent command (plus alternatives, per-cell notes, and cross-distro warnings) per manager. Runs locally: read-only, non-destructive, offline, contact

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYesQuery mode. "translate" needs action (and usually packages); "crossReferenceTable", "packageNameMap" and "presets" ignore the other fields and return their full static dataset.translate
actionNotranslate only. The package operation to render for each target manager. Required when operation is "translate".
packagesNotranslate only. Package name(s) substituted into the {pkgs} placeholder. A single whitespace-separated string is also accepted. Optional; install/remove/search-style actions warn and emit a <package> placeholder if omitted.
fromNotranslate only, optional. The source package manager you are translating from; recorded in the output notes for context only.
toNotranslate only, optional. Target package managers to render commands for, each one of apt/dnf/pacman/apk/zypper/pkg/brew/snap/flatpak/nix. Empty or omitted renders all 9.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the request succeeded.
operationNoThe operation that was executed, echoed back.
resultNoOperation-specific payload. "translate" returns action, packages (array), from (string or null), to (array of manager ids), commands (object keyed by manager with command, optional alternatives array, optional notes), plus warnings (array) and notes (array). "crossReferenceTable" returns actions (array), managers (array) and cells (action to manager to command + optional notes). "packageNameMap" returns an array of canonical/description/names where names maps each manager to its package name (empty if none). "presets" returns an array of id/label/description/action/packages.
Behavior5/5

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

Beyond the annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint), the description adds valuable context: it 'never runs a package manager', 'builds command strings from a static table', and is 'read-only, non-destructive, offline'. No contradictions with annotations.

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?

The description is appropriately sized for the tool's complexity, front-loading the core purpose and distinguishing from siblings. Each sentence earns its place, providing clear and necessary information without redundancy.

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?

Given the complexity (9 ecosystems, 4 operation modes) and the presence of a rich input schema and output schema, the description covers all essential aspects: what it does, how it works, when to use, and safety guarantees. It is complete for the intended use.

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 description coverage is 100%, so the baseline is 3. The description adds value by explaining the operation modes and how parameters interact (e.g., 'translate' needs action and usually packages; others ignore fields). This contextualizes the parameters beyond the schema, earning a 4.

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's purpose: to look up and cross-translate package-manager commands across 9 ecosystems. It uses specific verbs and resources, and distinguishes itself from sibling tools by naming them and specifying when to use each.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool versus alternatives: 'Use this for distro-specific package commands; use linux_command_builder for general find/grep/rsync/tar one-liners and linux_bash_script_generator for full scripts.' It also explains that the tool never runs commands and is safe.

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/Jambozx/onlinecybertools-mcp-server'

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