Skip to main content
Glama

Get security compliance overview

get_security_compliance_overview
Read-only

The organisation's compliance rollup across every scanned cluster: per cluster the benchmark results (CIS, NSA/CISA) with pass/fail counts, config-audit totals and scanner freshness, plus which clusters have no compliance data and why (baseline not enabled, agent offline). Read-only. Pulls the live trivy-operator compliance reports over the agent relay; a cluster that cannot be asked reads as not_available with a reason, never as compliant.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses the data source (live trivy-operator compliance reports over the agent relay) and the critical failure semantics: an unreachable cluster is reported as not_available with a reason, never as compliant. This is exactly the kind of behavioral context an agent needs.

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?

The description is front-loaded with the core purpose, then adds the return contents and finally the important read-only/source/failure semantics. It is dense but every sentence carries useful information.

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 must explain return values, and it does: per-cluster benchmark pass/fail counts, config-audit totals, scanner freshness, and clusters lacking data with reasons. For a no-parameter read-only overview, this is complete enough.

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

Parameters4/5

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

The tool has zero parameters, so there are no parameter semantics to explain and the baseline score is 4. The description appropriately focuses on output scope and behavior instead.

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 states a specific verb and resource: an organisation-wide compliance rollup across every scanned cluster, including benchmark results, config-audit totals, scanner freshness, and missing-data reasons. It is clearly distinguishable in scope from per-cluster or per-framework siblings, though it does not explicitly name those alternatives.

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?

The description implies usage as an organisation-level compliance overview by describing the rollup and its contents. However, it gives no explicit when-to-use guidance or alternatives versus siblings such as get_compliance_reports or get_security_compliance_framework_report.

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.