Skip to main content
Glama

Suggest a quieter run time

cron_suggest_slot
Read-onlyIdempotent

Suggests lower-load times for a new cron job over the next 24 hours, returning a cron expression, two alternatives, and the busiest time to help avoid scheduling conflicts.

Instructions

Suggest a time with fewer scheduled runs in the next 24 hours, as a cron expression with two alternatives and the busiest time. Use it when adding a job, then check the result with cron_validate_schedule.

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

Input Schema

NameRequiredDescriptionDefault
tzNoIANA time zone, such as America/New_York. Defaults to UTC.
periodNohourly picks a minute past each hour; daily picks a minute and an hour.hourly

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.2.73
    • addedInput schema / properties / period / default
      Added value: +"hourly"
    • addedInput schema / properties / period / description
      Added value: +"hourly picks a minute past each hour; daily picks a minute and an hour."
    • addedInput schema / properties / tz / description
      Added value: +"IANA time zone, such as America/New_York. Defaults to UTC."
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so credit here is for added context. The description adds the evaluation window (next 24 hours) and the composition of the response (two alternatives plus the busiest time), which annotations cannot convey. It does not say which jobs' schedules the suggestion is computed against, 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.

Conciseness5/5

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

A single tight sentence that front-loads what the tool produces before the operational guidance. No filler and 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 two-parameter, read-only, no-output-schema tool, the definition covers purpose, return shape, and next step, which is enough to call it correctly. The only missing piece is what data set the suggestion is derived from.

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%, so both parameters are already fully documented, including the enum semantics for 'period' and the IANA format for 'tz'. The description adds no further parameter guidance, so the baseline of 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 (suggest an off-peak time) plus the exact output shape: a cron expression with two alternatives and the busiest time. It is not explicitly contrasted with the closest sibling, cron_schedule_pressure, so an agent must infer the difference between 'suggest a slot' and 'report pressure'.

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?

Gives a clear trigger ('when adding a job') and an explicit follow-up step with cron_validate_schedule, which is strong sequencing guidance. It stops short of stating when *not* to use it or naming alternative planning tools (e.g. cron_schedule_pressure) for comparison work.

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