Skip to main content
Glama
Sign In
Apt MCP Server

Apt MCP Server

by GdMacmillan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

updateAptPackages

Refresh package index and upgrade all installed packages using sudo. Supports optional downgrades.

Instructions

Update the apt package list and upgrade all packages using sudo.

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": "updateAptPackages"
  }
}

Input Schema

NameRequiredDescriptionDefault
allowDowngradesNoAllow package downgrades during upgrade (e.g., when kernel transitions require it). Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations; description mentions sudo but fails to disclose risks of full upgrade, potential downtime, or error behavior for a destructive operation.

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?

Single, efficient sentence directly stating the action; no wasted words but lacks structure such as warnings or usage context.

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

Completeness3/5

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

For a simple tool with one optional parameter, the description is mostly complete but missing behavioral context like operation duration and success/failure reporting.

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% for the sole parameter; description adds no additional meaning beyond the schema's description.

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?

Clearly states the tool updates package list and upgrades all packages with sudo, distinguishing it from sibling tools like upgradeSpecificAptPackage.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus siblings like upgradeSpecificAptPackage or autoremoveAptPackages; no prerequisites or warnings.

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