Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
kubeguard_scanB

Audit Kubernetes manifest text. Returns findings with path:line evidence.

kubeguard_scan_pathC

Audit every YAML file under a local directory.

kubeguard_rulesA

List every rule with severity, rationale and fix.

kubeguard_rbacC

Effective permissions per subject after resolving all bindings.

kubeguard_demoC

Write a vulnerable sample manifest and audit it.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 5 tools

Disambiguation4/5

kubeguard_scan (inline manifest text) and kubeguard_scan_path (directory of YAML files) share the auditing purpose but have clearly different inputs, and the descriptions make that distinction explicit. kubeguard_demo also produces an audit but is framed as sample generation, so it is unlikely to be misselected. Only the scan/scan_path pair presents mild ambiguity.

Naming Consistency4/5

All tools use a uniform kubeguard_ snake_case prefix, which makes the family immediately recognizable. The suffix style mixes verbs (scan, scan_path, demo) with nouns (rules, rbac), a minor deviation from a pure verb_noun pattern but still readable and predictable.

Tool Count5/5

Five tools is well-scoped for a focused Kubernetes manifest auditor, and each tool covers a distinct capability: text scan, directory scan, rule catalog, RBAC analysis, and demo. There is no redundant or filler tool.

Completeness4/5

The set covers the core audit lifecycle: discovering rules, scanning inputs in two forms, analyzing RBAC, and a demo entry point for onboarding. Gaps are minor for a read-only auditor, but there is no way to apply or export fixes, suppress/config rules, or scan a live cluster, so agents must handle remediation outside the server.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues