Skip to main content
Glama

Get StatefulSets

get_statefulsets
Read-only

Fetch StatefulSet summary rows: name, namespace, replicas, ready and current counts, service name, age and the first unmet condition. Not-ready sets sort first. A list needs namespace or all_namespaces=true and carries total, returned, truncated and scope.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cluster_id": "<cluster_id>"
    },
    "name": "get_statefulsets"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoSpecific StatefulSet name to fetch.
namespaceNoKubernetes namespace to list. A list needs either this or all_namespaces=true; a named read (name) needs neither.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
all_namespacesNoSet true to list every namespace on the cluster deliberately. Omit it and pass namespace to list one namespace; a list with neither is refused (error_code scope_required).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description adds real operational traits beyond that: results are ordered with not-ready sets first, list responses report total/returned/truncated/scope, and a scope-less list fails. It stops short of describing permissions, rate limits, or the shape of a single named read response, so it is strong but not exhaustive.

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?

Two tight sentences: the first front-loads what is returned, the second covers ordering and the list/scope contract. Every clause carries distinct information with no filler or repetition.

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?

There is no output schema, so the description's field enumeration and truncation/scope reporting genuinely carry the return-value burden, and the list-vs-named-read distinction is covered. Minor gaps remain, such as what a single named read returns or how 'first unmet condition' is rendered, but an agent can call it correctly.

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%, so all four parameters (name, namespace, cluster_id, all_namespaces) are already documented, including the scope_required error on all_namespaces. The description restates the namespace/all_namespaces rule but adds no format or edge-case meaning the schema lacks; baseline 3 applies.

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?

"Fetch StatefulSet summary rows" names a specific verb and resource, and the enumeration of returned columns (name, namespace, replicas, ready/current, service name, age, first unmet condition) makes the scope unmistakable against siblings like get_deployments or get_daemonsets. An agent knows exactly which object family this targets without opening the schema.

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

Usage Guidelines4/5

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

The description states the scoping rule for list calls ('a list needs namespace or all_namespaces=true'), which tells the agent how to invoke it in list mode and implicitly contrasts with the named read. It does not name alternative tools (e.g. describe_resource or get_pods) for related needs, so there is no explicit exclusion guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.