Skip to main content
Glama

get_cronjob_status

Check whether a Kubernetes CronJob is running on schedule by comparing its cron schedule to the actual last run. Returns a verdict (on-schedule, late, missed, running, suspended), the next run time, and overrun details.

Instructions

Check whether a CronJob is running on schedule. Compares its cron schedule against the actual last scheduled run and returns a verdict: on-schedule, late, missed, currently running (or suspended), plus the next run time and whether runs take longer than the schedule interval (overrun: skipped, late or overlapping runs).

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": {
      "namespace": "<namespace>",
      "name": "<name>"
    },
    "name": "get_cronjob_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the CronJob
namespaceYesNamespace of the CronJob

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does substantial work: it enumerates the verdict values (on-schedule, late, missed, currently running, suspended), promises next run time, and explains the overrun concept (skipped, late, overlapping runs). Gaps remain around failure modes, e.g. what happens if the named CronJob does not exist, and no explicit read-only/safety statement beyond the word 'Check'.

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 with the purpose and scoping front-loaded, followed by a compact enumeration of what is returned. Every clause (verdicts, next run time, overrun) adds information rather than restating the name.

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?

Since there is no output schema, the description appropriately explains the return shape — verdict categories, next run time, overrun flag. It is nearly complete for a simple two-parameter read tool, with only error/not-found behavior left unaddressed.

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% for both parameters (name, namespace), so the schema already explains them fully. The description adds no syntax, format, or lookup-failure semantics for these parameters, so 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?

States a specific verb and resource ('Check whether a CronJob is running on schedule') and defines the tool's scope as schedule adherence rather than listing or history. This clearly separates it from siblings such as list_cronjobs, get_run_history, and find_silent_failures.

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?

Usage is implied by the purpose — use it to diagnose whether a job is on schedule, late, or missed — but the description never explicitly says when to pick it over get_run_history or find_silent_failures, nor does it state preconditions. An agent can infer the right context but must do the routing work itself.

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