Skip to main content
Glama

devops-linux

k8s_manifest_audit

Audit Kubernetes YAML/JSON manifests for missing resource limits, privileged securityContext, :latest tags, root containers, and probe readiness.

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

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does useful work by enumerating the specific violations detected, implying a non-mutating static analysis, but it never states that no changes are made, whether findings include severity or line references, or how results are returned.

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?

A single front-loaded sentence with no filler; the check enumeration is dense and scannable. The one weakness is that it spends its whole budget on checks and leaves nothing for input handling.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the description is the only source of behavioral information, yet it omits input mechanics entirely and says nothing about result format or severity reporting. For a two-input analysis tool this leaves real gaps an agent must resolve by guessing.

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

Parameters2/5

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

Two parameters exist at 0% schema description coverage, and the description says nothing about them. An agent must guess that 'text' means inline manifest content and 'filePath' a path on disk, and learns nothing about the relationship, precedence, or whether either is required.

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 names a specific verb and resource ('Audit Kubernetes YAML/JSON manifests') and enumerates the exact checks performed: resource limits, privileged securityContext, :latest tags, root containers, probe readiness. That enumeration distinguishes it from siblings like dockerfile_lint or k8s_resource_estimate without opening any schema.

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 check list implies when the tool is relevant (reviewing manifests before deployment), but there is no explicit guidance on prerequisites, when to prefer k8s_resource_estimate instead, or when the audit is not applicable. Usage must be inferred from the subject matter rather than stated.

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.

Resources