Skip to main content
Glama

Get addon security updates

get_addon_security_updates
Read-only

Which installed add-ons in the cluster run a version covered by a security advisory their upstream project published (GitHub security advisories and OSV), with a fix available: per add-on the advisory id, severity, one-line summary and link, the upstream release it runs, the release that fixes it, and the nearest chart version to upgrade to (upgrade_chart_version). Also lists the tracked add-ons that could not be judged, and how fresh the advisory data is (feed_checked_at, feed_stale) - an empty list on stale or unread data is not an all-clear. Read-only; Ankra does not upgrade add-ons on its own for advisories, the owner decides.

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": {
      "cluster_id": "<cluster_id>"
    },
    "name": "get_addon_security_updates"
  }
}

Input Schema

NameRequiredDescriptionDefault
addon_nameNoOptional: narrow the answer to one add-on by its name on the cluster (e.g. cert-manager).
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations only supply readOnlyHint=true; the description goes well beyond that by disclosing that non-matching add-ons are still listed as unjudged, that feed freshness is returned (feed_checked_at, feed_stale), and that an empty result under stale/unread data is not an all-clear. It also states the tool takes no remediation action. These are exactly the behavioral traits annotations cannot express.

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 front-loaded with the core question being answered, then layers the returned fields, the unjudged add-ons, and the freshness caveat in priority order. The opening sentence is long and carries a dense field enumeration, but every clause carries information an agent needs; nothing is filler.

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

Completeness5/5

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

There is no output schema, so the description carries the full burden of explaining return values, and it does: advisory identity, severity, link, current and fixed releases, upgrade_chart_version, unjudged add-ons, and freshness fields. For a two-parameter read-only report tool it leaves nothing essential for the agent to call or interpret it correctly.

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 both parameters are documented in the schema itself, including the UUID format and the list_clusters discovery hint. The description adds no parameter-level detail beyond implying per-add-on granularity; it never explains that addon_name narrows the result to a single add-on. Baseline 3 applies when the schema already does the work.

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 names a precise verb and resource: installed cluster add-ons running a version covered by a published upstream advisory that has a fix, with per-add-on advisory id, severity, summary, link, current release, fixing release, and upgrade_chart_version. That is far more specific than a tautology. It does not, however, distinguish itself from the close-sounding sibling get_cluster_addon_security or from get_application_security_versions, so the agent must infer the boundary from scope wording alone.

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 rather than stated: the tool is framed as an assessment whose outcome the owner acts on ('Ankra does not upgrade add-ons on its own for advisories, the owner decides'), which suggests this is a read/report step feeding a manual upgrade decision. The freshness caveat ('an empty list on stale or unread data is not an all-clear') gives real guidance on interpreting results. There is no explicit when-to-use statement, no exclusion, and no named alternative such as get_cluster_addon_security.

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.