Skip to main content
Glama

Schedule load

cron_schedule_pressure
Read-onlyIdempotent

Shows upcoming enabled cron runs grouped by hour and minute for a chosen time zone, revealing clustered jobs and idle minute slots so you can assess schedule pressure before adding work.

Instructions

Upcoming runs for enabled schedules over the next hours (default 24, max 168), grouped by hour and minute in tz (default UTC). Shows when jobs are scheduled together and which minute positions have no scheduled runs. Use it to see how busy each minute is; use cron_suggest_slot to pick a time for a new job.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cron_schedule_pressure"
  }
}

Input Schema

NameRequiredDescriptionDefault
tzNoIANA time zone to group the runs in, such as America/New_York. Defaults to UTC.
hoursNoHours ahead to scan.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.2.73
    • addedInput schema / properties / hours / default
      Added value: +24
    • addedInput schema / properties / hours / description
      Added value: +"Hours ahead to scan."
    • addedInput schema / properties / hours / maximum
      Added value: +168
    • addedInput schema / properties / hours / minimum
      Added value: +1
    • addedInput schema / properties / tz / description
      Added value: +"IANA time zone to group the runs in, such as America/New_York. Defaults to UTC."
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive and closed-world, so the safety bar is low. The description adds real behavioral detail: only enabled schedules are counted, defaults are 24h with a 168h cap, and empty minute positions are surfaced. It stops short of noting pagination/truncation limits or whether counts are per-minute frequency.

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 behavior front-loaded and the sibling routing placed last. Every clause earns its place.

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 must convey the return shape, and it does: runs grouped by hour and minute, plus which minute positions are empty. A note on the response being a fixed-size 24–168 hour structure would close the last gap.

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 both parameters (tz, hours) are already fully documented including default and max. The description restates the defaults and cap but adds no format or edge-case 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 specific verb+resource+scope: upcoming runs for enabled schedules over the next `hours`, grouped by hour/minute in a time zone. It also distinguishes the view's purpose ('how busy each minute is') from the sibling cron_schedule_duplicates / cron_suggest_slot, so the agent can tell what it returns without opening the schema.

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

Usage Guidelines4/5

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

Explicitly names the alternative — 'use cron_suggest_slot to pick a time for a new job' — and states the condition that selects this tool ('see how busy each minute is'). It does not state exclusions (e.g., disabled jobs, one-off runs), so it falls just short of full when/when-not coverage.

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