Skip to main content
Glama

kubeguard_rbac

Resolve RoleBindings in Kubernetes manifests to compute each subject's effective permissions. Use it to audit what a user, group, or service account can actually do without a live cluster.

Instructions

Effective permissions per subject after resolving all bindings.

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

Input Schema

NameRequiredDescriptionDefault
pathNo.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It states the conceptual output (effective permissions after binding resolution) but says nothing about whether this is read-only, which cluster/context it reads, whether it requires elevated privileges, or what the response shape looks like.

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 a single efficient sentence fragment with no filler, but it is under-specified rather than well-structured. There is no front-loaded verb or scope statement to orient the agent.

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 one unexplained parameter, no annotations, and no output schema, the description should explain the input semantics and basic behavior. It provides only a conceptual summary of the computation, leaving the agent unable to invoke it 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 `path` parameter has 0% schema description coverage, and the description never mentions it. With defaults to '.', the schema gives minimal implicit meaning, but the description adds no semantics about what path is used for (kubeconfig? manifest directory?) or whether it can be omitted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase identifies the domain concept (effective permissions per subject from resolved bindings), which is more specific than a tautology. However, it is a noun fragment with no verb, so the agent cannot tell whether the tool lists, computes, audits, or prints these permissions, and it does not differentiate itself from siblings like kubeguard_scan or kubeguard_rules.

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 when-to-use guidance, no prerequisites, and no mention of alternatives among the four sibling tools. The agent is left to infer from the name alone whether this is an audit, a report, or a query.

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