Skip to main content
Glama
Sign In
Apt MCP Server

Apt MCP Server

by GdMacmillan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

unholdAptPackage

Unhold specific apt packages to allow them to be upgraded again. Re-enable package updates by unholding package names.

Instructions

Unhold one or more apt packages to allow them to be upgraded again.

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

Input Schema

NameRequiredDescriptionDefault
packagesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the primary effect (unhold) without disclosing prerequisites (e.g., root permissions), reversibility, error behavior, or side effects.

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 a single sentence with no extraneous information. It is appropriately concise and front-loaded with the key action.

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 parameter and no output schema, the description covers the basic purpose. However, it lacks behavioral context (e.g., permissions, idempotency) that would be helpful for a complete picture.

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?

Schema coverage is 0%, and the description does not add meaning beyond the schema. It repeats 'one or more apt packages' which is already evident from the schema's array type and required field.

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 ('Unhold'), resource ('apt packages'), and purpose ('allow them to be upgraded again'). It effectively distinguishes from sibling tools like holdAptPackage and upgradeSpecificAptPackage by specifying the opposite action.

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 packages are held and need to be upgraded, but it does not explicitly state when to use this tool versus alternatives like holdAptPackage or when not to use it (e.g., if packages are not held).

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