Skip to main content
Glama
Sign In
SapperMCP

SapperMCP

by MasterX1582
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Package Remove

package_remove

Removes installed Linux packages and optionally purges their configuration files, supporting system cleanup during debugging or security hardening.

Instructions

Remove packages (apt-get remove -y). purge=True also removes config files.

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": {
      "names": "<names>"
    },
    "name": "package_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYes
purgeNo
timeoutNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does a good job: it discloses the exact command executed and the -y flag, which tells the agent the operation is non-interactive and cannot be confirmed at runtime. It also explains that purge removes config files, clarifying the permanence of that flag. It does not mention privilege requirements or what happens to dependent packages.

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?

Two sentences, no filler, and the primary operation is front-loaded ahead of the flag nuance. Every clause adds information an agent cannot get from the schema.

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?

The output schema is present, so return values need not be described, and the destructive mechanics are covered. However, for a destructive mutation with zero annotations, it should mention privilege/auth requirements, behavior for unknown package names, and side effects on dependent packages.

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 description coverage is 0% across three parameters, so the description must compensate and does so only partially: it explains purge's additive effect but says nothing about the shape of names or the meaning of timeout. The names parameter is inferable from the plural "packages", but timeout remains wholly undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Remove packages") and even names the underlying mechanism ("apt-get remove -y"), which immediately separates it from package_install, package_upgrade, and package_update. It does not explicitly name a sibling to contrast against, but the verb alone makes the operation unambiguous.

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?

Usage is implied by the verb: an agent can infer this is the tool for uninstalling software. There is no guidance on when to prefer this over package_update/package_upgrade, no preconditions, and no warning about dependents or partial-removal scenarios.

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