Skip to main content
Glama
Systems Manager

Systems Manager

Get Package Info

sm_system_get_package_info
Read-onlyIdempotent

Retrieve details for a single system package to verify version, status, or installation state before updates or troubleshooting.

Instructions

Get package info (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_get_package_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
packageNoSingle package name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data and the description is not required to repeat it. The description adds nothing beyond annotations — no note on cost, latency, what happens for a missing package, or the shape of the result — but with annotations this complete, that is a modest rather than severe gap.

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

Conciseness4/5

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

The definition is very short and front-loads the action, but the trailing family blurb about system health and updates is pure filler that does not help selection, and the parenthetical identifier is redundant with the tool name. Two sentences, one of which is entirely wasted.

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 read-only lookup whose main unknown is what data comes back and how the null-package case behaves, the description supplies neither, and there is no output schema to compensate. It is technically consistent with the annotations but leaves the agent guessing about results and about the optional-parameter path.

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 100% and the single 'package' parameter is documented as 'Single package name' with default null, so the schema carries the meaning. The description adds no interpretation beyond it — notably it does not explain the omitted-argument case (default null), which is the one ambiguity the schema leaves open.

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?

The description gives a verb-plus-resource phrase ('Get package info'), so the basic intent is readable, but 'package info' is never specified — no hint whether this returns version, dependencies, install state, or repository origin. It also does no sibling differentiation against nearby tools like sm_system_list_installed_packages or sm_system_search_package, and the parenthetical '(sm_system_operations)' plus the family blurb add no distinguishing detail.

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 is offered: nothing says to call this for a single known package versus using the list/search siblings to discover packages. The second sentence describes the whole tool family ('managing packages, system health, and updates') rather than this tool's invocation condition, so an agent gets no routing signal.

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