Skip to main content
Glama

Duplicate schedules

cron_schedule_duplicates
Read-onlyIdempotent

Find enabled jobs and workflow schedules with identical run times in the same time zone so you can spread them out and reduce scheduling collisions.

Instructions

Jobs with identical run times (for example, */5 and 0-59/5 in the same time zone), among enabled jobs and workflow schedules. Use this to find schedules that could be spread out; use cron_schedule_pressure for different schedules that share some minutes.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/ idempotent/ non-destructive/ closed-world, so the safety profile is covered. The description adds real behavioral content beyond that: only enabled jobs and workflow schedules are considered, implying disabled jobs are excluded from results, and timezone must match for duplication. It stops short of describing the shape of the returned groups, which is the only meaningful omission.

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 with no filler: scope and example first, then routing to the sibling. Front-loaded and every clause carries information, though the parenthetical example makes the opening sentence slightly denser than strictly necessary.

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 zero-parameter read tool with full annotation coverage, the description supplies what's needed to call it correctly and read it correctly (enabled-only, timezone-sensitive, duplicates vs shared-minute pressure). Since there is no output schema, the absence of any note about what the result groups look like is the one gap an agent might notice.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter guidance is needed or expected here.

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 precise resource — jobs with identical run times — and makes it concrete with the */5 vs 0-59/5 in the same time zone example. The scope ('among enabled jobs and workflow schedules') and the explicit contrast with cron_schedule_pressure let an agent distinguish it from siblings without opening anything else.

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 both the positive case ('Use this to find schedules that could be spread out') and the excluded case, naming cron_schedule_pressure as the alternative for different schedules sharing some minutes. The when-to-use decision is fully resolved in the description.

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