Skip to main content
Glama
Sign In
Apt MCP Server

Apt MCP Server

by GdMacmillan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

holdAptPackage

Prevent specified apt packages from being upgraded by placing them on hold. Use this to lock package versions in Debian/Ubuntu systems.

Instructions

Hold one or more apt packages to prevent them from being upgraded.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "packages": "<packages>"
    },
    "name": "holdAptPackage"
  }
}

Input Schema

NameRequiredDescriptionDefault
packagesYes

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 are provided, and the description does not disclose behavioral traits such as required permissions, side effects, or whether the action is reversible. For a system modification tool, this is insufficient.

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?

The description is extremely concise (one sentence, 12 words) and front-loaded. No redundant information, but could be improved by adding essential details without becoming verbose.

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

Completeness2/5

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

Given no annotations and no output schema, the description fails to cover prerequisites, error handling, or return values. It is incomplete for safe autonomous agent execution.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description must compensate but only minimally restates that packages are held. No examples, format guidance, or constraints beyond schema regex.

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 action ('Hold') and resource ('apt packages'), and specifies the purpose ('to prevent them from being upgraded'). It effectively distinguishes from siblings like unholdAptPackage and installAptPackage.

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

Usage Guidelines3/5

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

The description implies usage when preventing upgrades but does not explicitly state when to use this tool vs alternatives (e.g., unholdAptPackage for reversal). No context on prerequisites or consequences.

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