Skip to main content
Glama

Get DaemonSets

get_daemonsets
Read-only

Fetch DaemonSet summary rows: name, namespace, desired, current, ready and available node counts, age and the first unmet condition (or the unavailable count). 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_daemonsets"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoSpecific DaemonSet 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.4/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 adds meaningful behavior beyond that — not-ready sets sort first, list responses carry total/returned/truncated/scope, and the fallback to unavailable count when no condition exists. It stops short of saying what the default row cap is or how truncation is triggered.

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?

Three tight sentences: return shape first, then sort order, then scope requirements. No filler, and the most decision-relevant information (what a list requires) is present without hedging 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?

With no output schema, describing the returned fields and the truncation envelope is exactly the right compensation, and the mandatory scope rule is spelled out. What is left implicit is the row limit that produces truncation and any pagination mechanism for retrieving the remainder.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already documents all four parameters; the description mostly reinforces the same scope rule rather than adding new syntax or defaults. The one genuine addition is that a named read bypasses the namespace requirement entirely, which clarifies how name and namespace interact.

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?

States a specific verb (Fetch) and resource (DaemonSet summary rows) and then enumerates the exact columns returned, which makes it unmistakably distinct from get_deployments, get_statefulsets, and get_pods in the sibling set. An agent can pick this tool without opening its 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?

Explicitly states the two calling modes and their preconditions: a list requires namespace or all_namespaces=true, while a named read (name) needs neither, and a scopeless list is refused. It does not route the agent to alternatives such as describe_resource for full manifest detail, which is the only real gap.

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.