Skip to main content
Glama
Sign In
SapperMCP

SapperMCP

by MasterX1582
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Package Upgrade

package_upgrade

Upgrade installed packages via sudo apt-get upgrade -y, or set full to run dist-upgrade. Use it to apply available system package updates.

Instructions

Upgrade installed packages (apt-get upgrade -y, sudo). full=True runs dist-upgrade. Potentially long-running.

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

Input Schema

NameRequiredDescriptionDefault
fullNo
timeoutNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description does real work: it discloses that sudo is used (privilege requirement), that -y makes it non-interactive, and that it is 'Potentially long-running' (latency/timeout expectation). It does not state irreversibility, failure behavior, or whether a reboot may be needed after a kernel upgrade, which are material for an unannotated mutation tool.

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?

Three terse sentences with the core action first, then the flag behavior, then the operational caveat. Every clause carries information and nothing is padded.

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 two-parameter tool with an output schema, the description covers the main action, the mutation model, and the timing expectation, but omits the timeout parameter entirely and gives no sequencing guidance relative to package_update. An agent could call it, but could plausibly misuse the timeout or skip the index refresh.

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%, so the description must carry the parameters. It explains 'full' precisely (dist-upgrade vs plain upgrade) but never mentions 'timeout' (default 600) beyond the vague hint that the operation is long-running, leaving the agent to infer how to tune it.

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?

Names a specific verb and resource ('Upgrade installed packages') and grounds it in the concrete underlying command (apt-get upgrade -y with sudo), so the agent knows exactly what operation is performed. It stops short of differentiating itself from close siblings like package_update or package_install, so it isn't a 5.

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?

There is no explicit guidance on when to reach for this over package_update (refresh index) or package_install (add packages), and no stated prerequisites such as running package_update first. The only conditional offered is the full=True flag, which is parameter semantics rather than usage routing.

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