Skip to main content
Glama

List security namespaces

list_security_namespaces
Read-only

List the namespaces of the fleet (or of one cluster) with their security posture: scanned workloads, images and running pods, how many images carry a bill of materials, and the actionable findings by severity with known-exploited and fixable-severe counts. A row with report_scope 'cluster' and an empty namespace carries the node and control-plane images that belong to no namespace, so the rows add up to the cluster. Read-only. A namespace is usually one workflow, so start here before drilling into list_security_pods.

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": "list_security_namespaces"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
sortNoSort column: actionable (default), observed, critical, severity, workloads, images, pods, namespace, cluster_name, known_exploited, fixable_severe, last_scan.
orderNoasc or desc.
searchNoMatch namespace or cluster name.
page_sizeNoResults per page (default 50).
cluster_idNoRestrict to one cluster (UUID).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

The 'Read-only' sentence merely restates readOnlyHint=true, earning no credit, but the description does add real behavioral context beyond the annotation: the shape of each row, the special cluster-scope row with an empty namespace that carries node and control-plane images, and the guarantee that rows reconcile to the cluster total. Pagination and rate/limit behavior are left unstated, so this is solid but not rich.

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?

Front-loaded with the payload description, then the edge-case row explanation, then the routing hint — a sensible order with no filler. The middle sentence about report_scope is dense and assumes the reader knows that field exists in the output, which is a small readability cost.

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?

With no output schema, the description carries the burden of explaining return values, and it does so concretely: per-row metrics, severity breakdown, and the cluster-scope rollup row. It stops short of describing pagination metadata or total counts, which an agent would need to page 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%, so page, sort, order, search, page_size and cluster_id are already documented, setting the baseline at 3. The description adds only the implicit fleet-vs-cluster meaning of cluster_id and the fact that the posture metrics correspond to sortable columns; it never explains paging, search matching, or default ordering.

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?

States a specific verb (List) and resource (security namespaces) at both fleet and single-cluster scope, and enumerates exactly what each row conveys (workloads, images, pods, BOM coverage, findings by severity, known-exploited and fixable-severe counts). It is clearly distinguishable from the generic list_namespaces and from the drill-down list_security_pods it names.

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?

Gives an explicit sequencing recommendation — 'start here before drilling into list_security_pods' — plus the fleet-vs-one-cluster choice that maps to cluster_id. It does not state when to prefer the plain list_namespaces sibling or any exclusion condition, so the routing is clear but not 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.