Skip to main content
Glama
nucleusv

Linux MCP daemon

by nucleusv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

system/packages

Read-onlyIdempotent

List installed packages on Debian/Ubuntu (dpkg) or Alpine (apk) systems by parsing the package database. Filter by name (glob or exact) and get text or JSON output; read-only.

Instructions

Lists installed packages by parsing the package database (dpkg on Debian/Ubuntu, apk on Alpine); rpm-based systems return an error, not supported yet. Read-only. The whole list is returned with no cap (hundreds of entries), so filter with name: an exact name or a glob (openssh-*, *ssl*). Only packages with status installed are listed. Text has a header N packages installed (dpkg) and a NAME VERSION ARCH table; output_format: json returns an array of objects (name, version, architecture), [] when none; there are no description or size fields. For OS and kernel version use system/os-release.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOnly packages whose name matches this glob or exact name (e.g. 'openssh-*', '*ssl*', 'curl')
privilegedNoRun as root. Needs a grant for this tool in mcp-sudo.yaml, otherwise refused
output_formatNoUse json for structured output (yaml, table and wide return the same JSON); default is text

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.1
    • changedInput schema / properties / output_format / description
      Previous value: -"Desired output format (e.g. json, yaml, table, wide). Defaults to text"New value: +"Use json for structured output (yaml, table and wide return the same JSON); default is text"
    • changedInput schema / properties / privileged / description
      Previous value: -"Set to true to run as root"New value: +"Run as root. Needs a grant for this tool in mcp-sudo.yaml, otherwise refused"
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds substantial context beyond them: the unsupported rpm path, that the full list is uncapped (hundreds of entries), the installed-only filter, and exactly what the text and JSON outputs contain, including which fields are absent.

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?

Front-loaded with the core purpose and tightly packed with only useful facts; every clause carries information. It is dense and somewhat long as a single block, but there is no filler to cut.

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?

With no output schema, the description fully specifies the return shape for both text and JSON, notes empty-result behavior (`[]`), and covers platform limits and filtering. An agent has everything needed to call and interpret it correctly.

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 meaning: it explains why `name` matters (unbounded result set) and gives glob/exact examples, plus clarifies that output_format json returns an array of {name, version, architecture} objects and that other format values collapse to JSON.

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+resource (lists installed packages) and adds the mechanism (parsing dpkg/apk package database) plus the platform boundary (rpm-based systems error out). An agent can distinguish this from system/os-release and other system tools without opening a schema.

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?

Explicitly routes the agent: use this for installed packages, filter with `name`, and use `system/os-release` for OS/kernel version. It also states the when-not condition (rpm-based systems unsupported) and the scoping constraint (only status=installed).

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