Skip to main content
Glama

Get cluster security history

get_cluster_security_history
Read-only

The daily security posture trend of one cluster from its stored snapshots, oldest first: findings by severity, fixable critical/high, workloads and namespaces scanned, the risk score, the actionable / acknowledged / accepted-risk split, and the Kubernetes access posture summary the day recorded (access_posture; null on a day that recorded none, which is not a clean posture) per day in items. access_posture_history lists every day the access posture was recorded, also for a cluster without Trivy reports; vulnerability_snapshot_recorded false there means no scan that day, not zero findings. Read-only. A cluster with no snapshots yet (Trivy not installed or the snapshot loop not yet run) answers an empty items list, not an error - say so rather than reporting a clean history.

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_cluster_security_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days back to read, 1 to 365 (default 90); out-of-range values are clamped.
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

A3.7/5.0
Behavior4/5

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

Goes well beyond readOnlyHint=true by disclosing result ordering (oldest first), the empty-history case (Trivy not installed or snapshot loop not run returns an empty items list, not an error), the meaning of access_posture null (not a clean posture), the semantics of vulnerability_snapshot_recorded=false (no scan, not zero findings), and that access_posture_history covers days even without Trivy reports. It even instructs the agent to say so rather than report a clean history — strong defensive context. Missing only things like result size/pagination or how far back stored snapshots typically exist.

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?

Information density is high and almost nothing is wasted, but it is delivered as one very long multi-clause sentence whose key caveats (null access_posture, empty-history behavior) are buried mid-string rather than front-loaded. The final caveat about reporting an empty history is the most operationally important point and lands last.

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?

With no output schema, the description carries the full burden of describing the return shape, and it does: per-day items with the enumerated fields, plus the separate access_posture_history list and their differing day coverage. The failure-mode guidance (empty items, no scan) makes it sufficient for an agent to interpret results 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 coverage is 100%, so both parameters (days with its 1-365 range and clamping, cluster_id with the conversation-binding fallback) are already fully documented in the schema. The description restates the cluster scoping ('one cluster') but adds no syntax or format detail beyond the schema, 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?

Names a specific resource and scope: 'daily security posture trend of one cluster from its stored snapshots, oldest first', and enumerates the payload (findings by severity, fixable critical/high, workloads/namespaces scanned, risk score, disposition split, access posture). This clearly separates it from point-in-time posture tools, though it never names the sibling alternatives (list_security_cluster_posture, get_cluster_security_report_schedule, get_security_overview) that an agent must choose between.

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: 'trend ... per day' implies retrospective/historical questions versus a current-posture tool, and 'Read-only' frames it as a safe inspection. There is no explicit when-to-use/when-not-to-use guidance and no named alternative, so the agent must infer the boundary from the sibling list.

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.