Skip to main content
Glama

get_run_history

Lists retained CronJob runs newest first with start time, duration, status, pod exit code, and duration trend. Warns when history limits are too short to diagnose issues.

Instructions

List retained Jobs for a CronJob (newest first) with start time, duration, status and pod exit code, plus a duration trend. Warns when history limits are too short to be useful.

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_run_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the CronJob
limitNoMax runs to return
namespaceYesNamespace of the CronJob

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does disclose non-obvious traits: newest-first ordering, an aggregated duration trend, and a proactive warning when history limits are too short to be meaningful. What it omits is the safety profile (presumably read-only, implied by 'List'/'get') and behavior when a CronJob has zero retained runs.

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?

A single front-loaded sentence names the resource and the exact payload, with the warning behavior appended in a short clause. No filler and nothing buried.

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 correctly enumerates what comes back and in what order, and it flags the trend and warning side-effects. Only the empty-history case and the read-only nature are left implicit, which is a small gap for a simple listing tool.

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 namespace, name and limit are already fully documented in the schema. The description adds nothing about limit semantics beyond an indirect nod in 'history limits', so the baseline 3 applies.

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 (list retained Jobs for a CronJob) plus the returned fields (start time, duration, status, pod exit code) and ordering (newest first). It is clearly distinct from failure-oriented siblings like get_failure_details or find_silent_failures, though it never names an alternative explicitly.

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 only implied: you invoke it when you want the run history of one CronJob. There is no statement of when to prefer list_active_runs or list_recent_failures instead, and no prerequisites are mentioned.

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