Skip to main content
Glama

kubeguard_demo

Creates a deliberately vulnerable Kubernetes manifest in a target directory and audits it to demonstrate detection of misconfigurations.

Instructions

Write a vulnerable sample manifest and audit it.

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

Input Schema

NameRequiredDescriptionDefault
directoryNokubeguard-demo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries full burden: it says 'write' but not where files land, whether existing files are overwritten, what the vulnerable manifest contains, or whether the audit result is returned inline. Only the bare fact that filesystem mutation occurs is disclosed.

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?

One short sentence with no wasted words, and the action is front-loaded. However, the brevity here reflects under-specification rather than efficiency.

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?

For a tool with filesystem side effects, no annotations, no output schema, and an undocumented parameter, the description omits the essentials: write target semantics, overwrite behavior, and what the audit returns. An agent cannot call this confidently.

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?

The single parameter 'directory' has 0% schema description coverage and is never mentioned in the description. The default value 'kubeguard-demo' hints at behavior, but the description does not explain whether the directory is created, must exist, or is relative to cwd.

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 names a specific verb+resource pair: it writes a vulnerable sample manifest, then audits it. That distinguishes it from kubeguard_scan and kubeguard_scan_path, which audit existing content, but 'audit' is left vague about what auditing means here.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this demo tool versus kubeguard_scan or kubeguard_scan_path, whether it is a one-off sample/demo generator, or whether it is safe to run in a real cluster or repo. The agent has to infer usage from the word 'demo' in the name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.