Skip to main content
Glama
Sign In
Maintenant

Maintenant

by kOlapsis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

list_kubernetes_workloads

Read-only

List Kubernetes workloads grouped by namespace to check ready versus desired replicas and current status. Use it to spot deployments, StatefulSets, or DaemonSets that are unhealthy.

Instructions

List Kubernetes workloads (Deployments, StatefulSets, DaemonSets...) grouped by namespace, with ready/desired replica counts and status.

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

Input Schema

NameRequiredDescriptionDefault
agent_idNoFilter by agent/cluster UUID, or 'local'. Omit for all.
namespacesNoRestrict to these namespaces

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description then adds genuine behavioral value by disclosing the shape of the result: workloads grouped by namespace with ready/desired replica counts and status — important since no output schema exists. It omits pagination/limits and whether the call hits a live cluster API.

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?

A single front-loaded sentence with zero filler; the workload kinds appear in the parenthetical right where they disambiguate scope, and the returned fields follow immediately. Nothing in it is redundant ceremony.

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

Completeness4/5

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

For a simple two-parameter, read-only list tool with full schema coverage and no output schema, the description supplies the missing return-value picture (grouping and replica/status fields). Only minor gaps remain — result size, pagination, and freshness of the data — none of which block a correct invocation.

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?

Schema description coverage is 100%, with agent_id (including the 'local' sentinel and omit-for-all behavior) and namespaces both fully documented in the schema. The description adds only the loose notion of namespace grouping, which does not extend either parameter's semantics, so the baseline of 3 applies.

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?

Uses a specific verb (List) plus a named resource (Kubernetes workloads) and enumerates the concrete kinds covered (Deployments, StatefulSets, DaemonSets), which implicitly separates it from siblings like list_kubernetes_pods and list_kubernetes_nodes. It stops short of explicitly naming those siblings, so an agent must infer the boundary rather than read it.

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 never states when to use this over list_kubernetes_pods, list_kubernetes_namespaces, or list_kubernetes_nodes, and offers no exclusions. Usage is only implied by the resource type — an inventory/overview call — which is workable but leaves routing ambiguity for closely related sibling tools.

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