Skip to main content
Glama

Get jobs

get_jobs
Read-only

Fetch Job summary rows: name, namespace, completions, parallelism, succeeded/failed/active counts, start and completion time. Failed jobs 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_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoSpecific Job 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

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries the rest and does add real behavioral context: failed jobs sort first, list responses carry total/returned/truncated/scope, and a list without scope is refused with error_code scope_required. That is meaningful beyond the annotation, though rate limits, pagination mechanics, and cluster targeting behavior are not covered.

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 tight sentences, front-loaded with what is returned, then ordering, then scoping requirements. Dense but every clause carries information; only the field enumeration is slightly list-like filler.

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, the description steps in to describe the returned fields, envelope metadata (total, returned, truncated, scope) and sort order, which is exactly the missing piece. Remaining gaps are minor: no detail on error behavior beyond scope_required and no guidance on cluster_id discovery, though the schema covers the latter.

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 the meaning of name, namespace, cluster_id and all_namespaces is already documented, including the scope_required error. The description restates the namespace-or-all_namespaces rule without adding syntax, defaults, or edge-case semantics beyond the schema, which is the baseline 3 case.

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 and resource ('Fetch Job summary rows') and enumerates the returned fields, so the agent knows exactly what is produced. It does not differentiate itself from nearby siblings such as get_cronjobs or get_application_jobs, which keeps it shy of a 5.

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 scoping rule ('a list needs namespace or all_namespaces=true') and the note that a named read needs neither give implicit guidance on which mode to use. There is no explicit statement of when to prefer this over get_cronjobs, get_application_jobs, or get_pods, and no stated exclusions.

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.