Skip to main content
Glama
Systems Manager

Systems Manager

Search Package

sm_system_search_package
Read-onlyIdempotent

Search software packages by name to identify package details before managing system updates, installations, or system health checks.

Instructions

Search package (sm_system_operations). System operations for managing packages, system health, and updates

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

Input Schema

NameRequiredDescriptionDefault
packageNoSingle package name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds nothing beyond that — not what happens when the optional package argument is omitted, whether results come from a local index or a remote repository, or how many results to expect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very short and front-loaded, which is good, but the second sentence is filler that describes the broader module rather than this tool and therefore does not earn its place.

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?

For a one-parameter search tool with no output schema, the description should state what is returned and what an empty/null package argument means. Neither is covered, leaving the agent guessing about result shape and default scope.

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 coverage is 100% with a single optional parameter already documented as "Single package name", so the baseline is 3. The description contributes no additional meaning such as whether omitting the parameter implies a wildcard search.

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

Purpose3/5

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

"Search package" names a verb and resource, but the second sentence ("System operations for managing packages, system health, and updates") is a generic module blurb rather than a description of this tool. Nothing explains what is searched (installed packages, repositories, available updates) or how it differs from siblings like sm_system_list_installed_packages or sm_system_get_package_info.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives despite many overlapping system/package siblings. The agent must infer from the name alone that this is a lookup rather than a listing or info tool.

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