Skip to main content
Glama

Get CronJobs

get_cronjobs
Read-only

Fetch CronJob summary rows: name, namespace, schedule, suspend, active jobs, last schedule and last successful time. 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_cronjobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoSpecific CronJob 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.8/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: it discloses the returned row shape and, importantly, that list responses carry total, returned, truncated and scope — telling the agent results may be truncated and must be interpreted through those fields. There is no output schema, so this return-shape disclosure is genuinely additive. It could still say more about ordering or truncation thresholds.

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 sentences, zero filler, and the resource plus returned fields are front-loaded before the scoping constraint. Nothing is repeated and nothing could be cut without losing information.

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 four parameters, full schema coverage, and no output schema, the description covers the essentials: what a row contains, how listing is scoped, and that responses are truncated with scope metadata. The remaining gaps are minor — no note on ordering, no clarification of how a named read differs in shape from a list row.

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 every parameter is already documented, including the namespace/all_namespaces interplay and the scope_required error. The description restates that same rule without adding new meaning such as name-matching semantics, defaults, or whether name and namespace can be combined. Baseline 3 is appropriate.

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?

The description opens with a specific verb and resource ("Fetch CronJob summary rows") and enumerates the returned fields (name, namespace, schedule, suspend, active jobs, last schedule, last successful time), which distinguishes it from adjacent workload tools like get_jobs or get_deployments. It stops short of naming any sibling explicitly, so the differentiation relies on the reader inferring that CronJobs are not Jobs.

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?

It does state the scoping rule: a list requires namespace or all_namespaces=true, while a named read needs neither. That is operational guidance rather than when-to-use guidance — there is no mention of when to pick this over get_jobs or describe_resource, and no exclusions or preconditions such as required cluster access.

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.