Skip to main content
Glama

Resource usage

cron_get_job_resources
Read-onlyIdempotent

Retrieve CPU and RSS time series for a job's live and recent runs, plus its resource limit caps and whether each capped run applied them or hit its memory cap.

Instructions

CPU/RSS time series for a job's live and recent runs (monitorResources jobs), plus its resourceLimits caps and each capped run's limits record, which says whether the caps applied and whether the run hit its memory cap. Use it for one job's resource use; use cron_get_node for the whole host, or cron_query_metrics for Prometheus samples.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields 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."
    • addedInput schema / properties / runs / default
      Added value: +200
    • addedInput schema / properties / runs / description
      Added value: +"Most recent recorded runs to include (default and maximum 200)."
    • addedInput schema / properties / runs / maximum
      Added value: +200
    • addedInput schema / properties / runs / minimum
      Added value: +1
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Adds context beyond the readOnly/idempotent annotations: it explains what the limits record conveys (whether caps applied and whether the memory cap was hit) and that it covers live plus recent runs. It doesn't mention error/empty behavior for jobs with no monitorResources runs, leaving a small gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the returned data, then the sibling routing. Slightly dense with clauses, but every clause carries information the agent needs.

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?

Covers scope, payload shape and alternatives for a read-only query tool with no output schema. Return values aren't fully specified (series format, limits record fields), but the nature of the output is conveyed well enough for selection.

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% and both parameters are documented there, including the unknown-name error and the runs cap of 200. The description adds no parameter-level detail, so the 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 the resource returned (CPU/RSS time series), the scope (one job's live and recent monitorResources runs), and the extra payload (resourceLimits caps plus per-run limits records). It is clearly distinguishable from host-wide and metrics-query siblings.

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 says 'use it for one job's resource use' and names two alternatives with their conditions: cron_get_node for the whole host, cron_query_metrics for Prometheus samples. Routing is unambiguous.

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