Skip to main content
Glama

SLA trends

cron_get_job_trends
Read-onlyIdempotent

Analyze a cron job's success rate and duration trends across 1h, 24h, 7d, 30d, or all history to detect increasing failures or longer runtimes.

Instructions

Per-window (1h/24h/7d/30d/all) success-rate and duration statistics from the saved run history for one job. Use it to see whether a job fails more often or runs longer than it used to; use cron_list_runs for the runs behind the numbers.

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

Input Schema

NameRequiredDescriptionDefault
nameYesExact job name, as cron_list_jobs returns it. An unknown name returns an error.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.73
    • 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, idempotentHint, and closed-world behavior, so safety is covered. The description adds provenance ('from the saved run history'), which tells the agent the numbers are historical rather than live. It does not say how short or missing history is handled per window, nor whether stats are cached or fresh.

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, with the core scope front-loaded and the sibling handoff placed after it. Every clause carries 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?

For a simple read-only stats tool with no output schema, the description sketches the return content (per-window success rate and duration) and points to where raw runs live, which is enough to call it correctly. Slight gap on what an empty or partial history returns for a given window.

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?

Only one parameter and schema coverage is 100%, so the schema already explains that an exact job name matching cron_list_jobs output is required and that an unknown name errors. The description adds no further meaning about the name argument, making 3 the baseline.

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: per-window success-rate and duration statistics from saved run history for one job. The window set (1h/24h/7d/30d/all) pins down the output granularity, which no sibling does.

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?

Explicitly names the use case (spotting jobs that fail more often or run longer than before) and routes the agent to the correct alternative (cron_list_runs) for the underlying runs. The condition that selects each tool is unambiguous.

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