Skip to main content
Glama
Sign In
KubeCraft MCP Server

KubeCraft MCP Server

by cloudcrafttech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List GPU Workloads

list_gpu_workloads

List Kubernetes pods using GPU resources with node, phase, requests, and limits.

Instructions

List pods that request or limit GPU extended resources (e.g. nvidia.com/gpu) with node, phase, requests, and limits.

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

Input Schema

NameRequiredDescriptionDefault
namespaceNoKubernetes namespace (omit for all namespaces)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

Without annotations, the description fails to disclose whether the operation is read-only or any required permissions. It only states what it lists but not behavioral traits like safety or performance.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that efficiently conveys purpose, resource, and output fields. No verbosity.

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

Completeness3/5

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

The description covers the essential purpose and output fields, but lacks additional context such as default namespace behavior or output structure details. Given the simplicity of the tool, it is minimally complete.

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

Parameters3/5

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

The input schema already provides full description for the only parameter 'namespace'. The description adds no additional parameter semantics beyond the schema.

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 clearly states the tool lists pods that request or limit GPU extended resources, with example resource (nvidia.com/gpu) and output fields (node, phase, requests, limits). This differentiates it from generic list_pods and other list tools.

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 description implies usage for listing GPU-requesting pods, but does not provide explicit guidance on when to prefer this over list_pods or other list tools. No exclusions or alternatives are mentioned.

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

Deploy Server

Other Tools