Loading ToolBench

Reading the current corpus…

kubernetes-mcp-server MCP server · F · ToolBench

← Browse

kubernetes-mcp-server

github.com/ArangoGutierrez/kubernetes-mcp-server

Model Context Protocol server for Kubernetes cluster management with special support for OpenShift

2026-07-28+STDIO3 tools

38/100

Definition Quality30

Protocol Readiness50

Supportability44

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence · detected: Dynamic Client Registration

Deprecated protocol patterns detected

Summary

Three tools with minimal documentation. Tool names follow verb_noun pattern (list_*), which is good. However, descriptions are extremely brief (12-28 chars), far below the 194-char baseline. No input schemas visible in provided source code, only test file references. Parameters are not documented. Output schemas are not specified. No error handling guidance. This server lacks the foundational definition quality needed for production agent use.

Tools (3)

configuration_contexts_listread onlysource verified30/100

List available Kubernetes contexts from kubeconfig

events_listread onlysource verified30/100

List Kubernetes events

namespaces_listread onlysource verified30/100

List Kubernetes namespaces

Issues (5)

CRITICALtool ↗

No input schemas visible in source code. Tool definitions appear to be inferred from test files only (mcp_tools_test.go, tool_filter.go). Cannot verify parameter types, constraints, or structure.

namespaces_listevents_listconfiguration_contexts_list

CRITICALtool-description ↗

Descriptions are 12 - 28 characters, far below the 194-char baseline. 'List Kubernetes namespaces' and 'List Kubernetes events' lack context for when to use each tool, what they return, or dependencies. LLMs cannot distinguish between similar tools with such minimal guidance.

namespaces_listevents_listconfiguration_contexts_list

CRITICALtool-description ↗

No parameter documentation visible. Cannot verify that parameters have descriptions, types, or constraints. LLMs will guess at parameter meaning and valid values.

namespaces_listevents_listconfiguration_contexts_list

Recommendations

Expand each tool description to 100 - 200 characters. Example: 'namespaces_list' → 'List all Kubernetes namespaces in the current context. Returns namespace names, status, and creation timestamps. Use this to discover available namespaces before querying resources.'
Document all input parameters with type, description, and constraints. Example: 'context_name (string, optional): Kubernetes context to query. If omitted, uses current context from kubeconfig.'
Document output schema for each tool. Example: 'namespaces_list returns {namespaces: [{name: string, status: string, created_at: ISO8601}], total_count: number}'
Add error handling guidance. Example: 'If kubeconfig is not found, error message will suggest setting KUBECONFIG env var or running 'kubectl config view'.'
Distinguish between tools: 'namespaces_list' lists namespace metadata; add a separate 'namespace_describe' tool if detailed namespace info is needed. Avoid tool name ambiguity.

Score history

Overall score trend

First recorded score · v2 rubric

38/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	38	2026-07-28+	v2