Skip to main content
Glama

Get security overview

get_security_overview
Read-only

The organisation's fleet-wide Security Center summary: finding totals by severity, how many are fixable, CISA known-exploited exposure, exploit-intelligence coverage, scanner coverage and freshness, the top remediation candidates, and access_posture: how many clusters have a standing cluster-admin grant, a grant over the access policy, a grant verified able to impersonate, or an access posture that could not be fully verified (counted as unverified, never as clean; null under an add-on scope). Optionally scoped to one cluster or one add-on. Read-only. This is the fleet rollup; get_security_reports is the per-cluster Trivy summary.

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

Input Schema

NameRequiredDescriptionDefault
addon_slugNoScope the overview to one add-on.
cluster_idNoScope the overview to one cluster (UUID); omit for the whole fleet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and the description confirms 'Read-only', so the safety profile is not new information. Where it adds genuine value is the disclosure that an unverifiable access posture is 'counted as unverified, never as clean' and is null under an add-on scope — non-obvious counting semantics an agent could otherwise misread as a clean result.

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?

It is front-loaded with the resource and ends with a useful disambiguation sentence, but the first sentence is a very long comma-and-'and' chain enumerating fields, which hurts scannability. Every element is substantive, yet a bulleted or clause-separated rendering would carry the same information more efficiently.

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 only two optional parameters, a readOnly annotation, and no output schema, the description carries the full burden of explaining return content — and it does so field-by-field, including the edge cases (unverified posture, null under add-on scope). Nothing an agent needs to call it or interpret the result is missing.

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?

Schema coverage is 100%, so both parameters are already documented. The description still adds meaning beyond the schema by explaining the interaction between scoping and the access_posture field (null under an add-on scope), which tells the agent how filtering changes the shape of the returned data.

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+resource+scope ('The organisation's fleet-wide Security Center summary') and then enumerates the exact contents: severity totals, fixable counts, CISA known-exploited exposure, exploit-intel coverage, scanner coverage/freshness, top remediation candidates, and access_posture. It explicitly names the sibling it is not ('get_security_reports is the per-cluster Trivy summary'), so an agent can route between them without opening either schema.

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?

It gives clear use context ('fleet rollup' vs per-cluster Trivy summary in get_security_reports) and states that scoping to one cluster or one add-on is optional. It does not address adjacent siblings such as get_security_compliance_overview or list_security_cluster_posture, so the alternative routing is only partially covered rather than exhaustive.

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.