Skip to main content
Glama

Get deployments

get_deployments
Read-only

Fetch deployment summary rows: name, namespace, replicas, ready/available/updated counts, age and the first unmet condition (Available, Progressing). Not-ready deployments 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_deployments"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoSpecific deployment 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).
label_selectorNoLabel selector to filter deployments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 still adds genuinely new behavior: not-ready deployments sort first, and list responses carry total/returned/truncated plus scope. That ordering guarantee and truncation signal are exactly the kind of operational detail annotations do not convey.

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

Conciseness4/5

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

Three dense sentences, front-loaded with what is returned and then the scoping rule; almost no filler. The trailing list of response envelope fields is slightly checklist-like but each item is substantive.

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, and the description compensates by naming the returned fields and the list envelope (total/returned/truncated/scope). What remains uncovered is minor formatting detail such as the type of age or condition values, so it is complete enough to call 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 coverage is 100%, so every parameter including the scope_required error case is already documented in the schema. The description restates the namespace/all_namespaces rule rather than adding syntax or semantics beyond it, which is the baseline expectation when the schema does the heavy lifting.

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?

States a specific verb (fetch) and a precise resource (deployment summary rows) and enumerates the exact columns returned (name, namespace, replicas, ready/available/updated, age, first unmet condition). This clearly distinguishes it from pod/node tools, though it does not name the adjacent deployment-oriented siblings (get_stack_deployments, get_application_deployments), so an agent must infer the boundary.

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?

Gives one concrete usage rule: a list requires either namespace or all_namespaces=true, while a named read needs neither. However there is no explicit guidance on when to choose this over describe_resource or the stack/application deployment variants, so the when-to-use-vs-alternative question is only partly answered.

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.