Skip to main content
Glama
AgenSysAdmin

AgenSysAdmin

by E13ctr0N

check_updates

Read-only

Read available apt package updates from the existing cache without refreshing it; results may be stale.

Instructions

Read available updates from the existing apt cache without refreshing it. Results may be stale.

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": {
      "server": "<server>"
    },
    "name": "check_updates"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverYes
security_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing that no cache refresh occurs and that returned data may be stale, which affects how the agent should treat the results. It omits output shape and any permission/connectivity prerequisites.

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 short sentences with zero filler, and the key constraint (cache-only read) is front-loaded before the staleness caveat. Every sentence earns its place.

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 tool is simple and read-only, and the cache/staleness caveat is the most important thing to convey. But with no output schema and no parameter documentation, the description leaves the return value (list of packages? counts?) and the effect of security_only entirely unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden for the two parameters, yet it mentions neither. In particular, "security_only" is non-obvious (filter to security updates only?) and "server" selection is unexplained, so an agent gets no semantic help beyond bare property names.

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?

The description gives a specific verb and resource ("Read available updates") and adds a meaningful scope qualifier: it reads from the existing apt cache rather than refreshing. That distinguishes it from a hypothetical refresh/apply tool. It stops short of naming any sibling (e.g., full_security_audit or security_audit) it should be chosen over.

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?

"Without refreshing it" implies the use case (fast, offline, no network or cache mutation), and "results may be stale" implies when to avoid relying on it. However, it never states explicitly when to prefer this over the audit siblings, nor what to do if freshness matters, leaving the agent to infer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.