Skip to main content
Glama
Sign In
SapperMCP

SapperMCP

by MasterX1582
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Package List Installed

package_list_installed

Lists installed dpkg packages and returns matching names, with optional substring filtering and a result limit for system inspection.

Instructions

List installed packages (dpkg). filter = name substring.

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_list_installed"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
filterNo

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?

No annotations are supplied, so the description carries the full behavioral burden; it discloses the dpkg data source and that filtering is a substring match on name, which are genuinely useful traits. However, it says nothing about truncation or result ordering even though a limit parameter with a default of 500 implies results may be silently capped.

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 ultra-short sentences with the resource stated first and the parameter note second; nothing is wasted. The fragment style ("filter = name substring.") is terse but unambiguous and appropriately sized for a two-parameter list tool.

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?

An output schema exists, so return values need not be described, and the core operation is adequately conveyed. Still, for a tool that can return hundreds of packages under a default limit, the absence of any note about capping, ordering, or case sensitivity leaves a meaningful gap.

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 compensate; it does add real meaning for filter ("name substring"), clarifying both the matched field and the match mode, which the bare anyOf string schema does not convey. The limit parameter gets no explanation at all, leaving its truncation semantics 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 ("List installed packages") and identifies the underlying backend as dpkg, which meaningfully narrows scope versus a generic package tool. It does not name or contrast any sibling such as package_search, so the agent must infer the installed-vs-available distinction from the word "installed" alone.

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 when-to-use guidance, no exclusions, and no named alternative. The only hint is the parenthetical "(dpkg)", which lets an agent guess this is Debian-family only, but nothing tells it when to prefer this over package_search or package_info.

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