Skip to main content
Glama
watchcron

watchcron-mcp

Official
by watchcron

create_monitor

Creates a cron job monitor with interval or cron expression schedules and returns a ping URL to detect missed or late runs.

Instructions

Create a new cron job monitor. Returns the ping URL that your cron job should call. Supports simple interval (every N seconds) or cron expression schedules.

Input Schema

NameRequiredDescriptionDefault
nameYesMonitor name (e.g. 'Daily backup', 'DB cleanup')
tagsNoTags for organizing monitors
timezoneNoTimezone (e.g. 'UTC', 'America/New_York')
descriptionNoOptional description
grace_secondsNoGrace period in seconds before alerting (default: server default)
schedule_typeYesSchedule type: 'simple' for fixed interval, 'cron' for cron expression
period_secondsNoInterval in seconds (required for simple schedule, min 60)
cron_expressionNoCron expression (required for cron schedule, e.g. '*/5 * * * *')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the tool returns a ping URL and supports two schedule modes, but it does not mention permissions, side effects, uniqueness constraints, or failure behavior for a mutation operation.

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?

Three short sentences front-load the core action, then cover the return value and scheduling modes. There is no redundant or filler language.

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?

Given 8 parameters, full schema coverage, and no output schema, the description covers the essential points: what is created, what is returned, and how scheduling works. The main remaining gap is the lack of annotation-backed safety context, which is a behavioral rather than structural omission.

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 all eight parameters are already documented in the input schema. The description reinforces the schedule_type distinction between simple interval and cron expression, but adds no syntax or validation detail beyond the schema.

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?

The description states a specific verb and resource ('Create a new cron job monitor') and immediately distinguishes the operation from siblings like list_monitors, update_monitor, and delete_monitor. It also names the supported schedule modes, making the tool's role unambiguous.

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

Usage Guidelines3/5

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

The description makes clear that this is the tool for creating a monitor, but it does not explicitly say when to use it versus alternatives such as update_monitor or pause_monitor. Usage is implied by the verb 'Create' rather than stated through explicit routing guidance.

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