Skip to main content
Glama

Run history

cron_list_runs
Read-onlyIdempotent

Show saved run history, success rate, and duration statistics for one cron job, newest run last, to inspect individual runs.

Instructions

Show saved run history, success rate, and duration statistics for one job, newest run last. Use it to inspect individual runs; use cron_get_job_trends for success rates over fixed windows, or cron_why_no_run when an expected run is missing.

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

Input Schema

NameRequiredDescriptionDefault
nameYesExact job name, as cron_list_jobs returns it. An unknown name returns an error.
limitNoMost recent runs to return (default and maximum 200).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.2.73
    • addedInput schema / properties / limit / default
      Added value: +200
    • addedInput schema / properties / limit / description
      Added value: +"Most recent runs to return (default and maximum 200)."
    • addedInput schema / properties / limit / maximum
      Added value: +200
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / name / description
      Added value: +"Exact job name, as cron_list_jobs returns it. An unknown name returns an error."
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only the result ordering ('newest run last') and that data is 'saved'; it says nothing about response volume, truncation when more than 200 runs exist, or latency. With annotations carrying the behavioral load, this modest addition lands at 3.

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 waste: the capability and scope come first, the routing guidance second. Every clause earns its place, including the ordering note.

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?

No output schema exists, but the description enumerates what comes back (run history, success rate, duration statistics) and defines ordering, which is enough for an agent to call and consume it. A minor gap is what happens with jobs having more runs than the 200 limit.

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%: the schema already documents 'name' (exact job name, error on unknown) and 'limit' (default and max 200). The description only restates the 'one job' scoping and 'newest run last' ordering rather than adding syntax or format guidance beyond the schema, 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 concrete verb and resource set ('Show saved run history, success rate, and duration statistics') scoped to 'one job', plus output ordering ('newest run last'). It also names the sibling tools it is not, so an agent can distinguish it from cron_get_job_trends and cron_why_no_run without reading schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use ('inspect individual runs') and names two alternatives with the conditions that select them: cron_get_job_trends for success rates over fixed windows, cron_why_no_run when an expected run is missing. Nothing is left to inference.

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