Skip to main content
Glama

Get cluster addon security

get_cluster_addon_security
Read-only

The security posture of one add-on on one cluster: the workloads attributed to it with their images, the observed and actionable findings by severity, known-exploited and fixable-severe counts, the dispositions in force, and scanner freshness. Read-only. The organisation-level view of the same add-on is get_security_overview with addon_slug.

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": {
      "addon_name": "<addon_name>"
    },
    "name": "get_cluster_addon_security"
  }
}

Input Schema

NameRequiredDescriptionDefault
addon_nameYesThe add-on's name on the cluster (its release name, e.g. trivy-operator, cert-manager).
cluster_idNoCluster id (UUID). Optional when the conversation is bound to a cluster.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

readOnlyHint already declares safety, so the 'Read-only' sentence is redundant, but the description adds substantial behavior beyond annotations: it enumerates what the response contains (attributed workloads with images, observed vs actionable findings, KEV/fixable-severe counts, dispositions, scanner freshness). With no output schema, this disclosure is the main source of return-value context.

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?

Three sentences, front-loaded with the scope, then the read-only constraint, then the disambiguation pointer. The long enumeration earns its length because no output schema exists to describe the payload.

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?

For a two-parameter read tool with annotations covering safety, the description is nearly complete: scope, payload contents, and the org-level alternative are all covered. Minor gap is the lack of differentiation from other add-on/cluster security tools that could plausibly return overlapping data.

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 schema already explains addon_name (release name, with examples) and cluster_id (UUID, optional when the conversation is bound to a cluster). The description adds no further parameter semantics, so the baseline of 3 applies.

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 the exact resource and scope: security posture for one add-on on one cluster, enumerated as workloads/images, findings by severity, KEV and fixable-severe counts, dispositions, and scanner freshness. It distinguishes itself from the organisation-level sibling get_security_overview, though it does not contrast with nearby siblings like get_cluster_stack_security or get_addon_security_updates.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing guidance is given for the main ambiguity: use get_security_overview with addon_slug for the organisation-wide view of the same add-on. The read-only nature is stated, but there is no guidance on when this is preferable to other per-cluster security tools such as get_cluster_stack_security or list_security_findings.

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.