Skip to main content
Glama

Get OS patch status

get_os_patch_status
Read-only

Report the rolling OS security-patch lane's state on an Ankra-provisioned cluster: the patch policy (enabled for automatic runs or not, the UTC maintenance window and when it next opens, the cadence, whether stateful nodes are included, the security-lag threshold), the newest run with each host's step (status, what was upgraded, whether it rebooted, why a host was skipped, the error that stopped the run), the last recorded dry run, and security_lag - behind when held-back security updates have been pending longer than the threshold, unknown when no dry run has been recorded yet (that is not the same as none). It also records a finished run or dry run it finds, so the answer never trails the operations it reports. A plain read: nothing on the cluster is touched.

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

Input Schema

NameRequiredDescriptionDefault
cluster_idNoUUID of the cluster. Optional when a cluster is selected.
cluster_nameNoExact name of the cluster. Optional when a cluster is selected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses a genuinely non-obvious behavioral trait: the tool "also records a finished run or dry run it finds," so a read can reconcile internal run state. It also explains the security_lag tri-state, including that "unknown" (no dry run recorded) differs from "none". The "nothing on the cluster is touched" line largely restates the annotation, and auth/prerequisite requirements are not covered.

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?

The purpose is front-loaded and each clause does convey real return-value detail, so little is pure padding. But the core is a single run-on sentence with a long parenthetical list of policy fields, which is harder to parse than a short bulleted enumeration would be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly carries the burden of describing returns, and it does so thoroughly (policy fields, per-host run steps, dry run, security_lag semantics). What remains thin is the cluster-resolution behavior for the two optional parameters and the absence of explicit pointers to the mutation siblings.

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% for both cluster_id and cluster_name, so the schema already carries the parameter meaning and the high-coverage baseline of 3 applies. The description never mentions cluster identification or what happens when neither identifier is supplied, so it adds no semantic value over the schema.

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

Purpose5/5

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

The description opens with a specific verb and resource ("Report the rolling OS security-patch lane's state on an Ankra-provisioned cluster") and then enumerates exactly what is reported: patch policy, newest run with per-host steps, last dry run, and security_lag. That enumeration distinguishes it from siblings such as run_os_patches, plan_os_patches, and set_os_patch_policy, which act on the same domain.

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?

Usage is implied by the closing line "A plain read: nothing on the cluster is touched," which tells the agent this is the non-mutating option, and by the detailed content list, which signals when a status read is appropriate. However, no sibling is named and no when-not rule is given (e.g., use set_os_patch_policy to change the policy, run_os_patches to trigger a run).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.