Skip to main content
Glama

cron_create

Create a scheduled trigger. Schedule is a 5-field cron expression (minute hour dom month dow). It uses UTC by default; an IANA timezone such as America/Los_Angeles gives local wall-clock scheduling with daylight-saving changes handled automatically. Each fire dispatches a job to your handler (at-least-once delivery, so handlers are idempotent). Missed fires during platform downtime are NOT replayed.

Common patterns:

Pattern

Schedule

Every 15 minutes

*/15 * * * *

Daily at 08:00 UTC

0 8 * * *

Every 6 hours

0 */6 * * *

Weekly Monday midnight

0 0 * * 1

Minimum interval. Your plan sets the smallest gap allowed between two fires. cron_list({ project_id }) reports it as policy.min_interval_minutes, alongside policy.max_per_project. A schedule tighter than the floor is refused with CRON_SCHEDULE_TOO_FREQUENT and the message names both intervals. Schedules that already exist are never re-checked — they keep firing on the cadence they were created with.

Example:

{
  "project_id": "my-saas",
  "name": "daily-digest",
  "schedule": "0 8 * * *",
  "handler": "https://my-saas.somewhere.site/api/cron/daily-digest",
  "payload": { "type": "digest" }
}

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": {
      "project_id": "<project_id>",
      "schedule": "<schedule>",
      "handler": "<handler>"
    },
    "name": "cron_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional display name, shown in the dashboard.
enabledNoOptional. Whether the trigger should fire. Defaults to true.
handlerYesProject-relative /api path or full https:// URL the platform POSTs to on each fire.
payloadNoOptional JSON object or JSON string — becomes the POST body on each fire.
scheduleYes5-field cron expression in the selected timezone (UTC when omitted). Must not fire more often than the plan floor reported by cron_list.
timezoneNoOptional IANA timezone, e.g. America/Los_Angeles. Defaults to UTC; daylight-saving transitions are handled by the scheduler.
project_idYesProject ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly=false, idempotent=false, destructive=false) by disclosing at-least-once delivery, the requirement that handlers be idempotent, that missed fires during downtime are NOT replayed, DST handling for timezones, and the exact error code and message shape for policy rejection. This is exactly the operational context the annotations cannot carry.

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?

Front-loaded with the core definition, then constraints, then a pattern table and example — good scannable structure with no filler sentences. Slightly long, and the example JSON partly restates what the schema and table already convey.

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 7-parameter creation tool with no output schema, it covers scheduling semantics, constraints, error behavior, and timezone handling thoroughly. The remaining gap is that it never says what a successful create returns (trigger id, next fire time), which an agent needs to chain further calls.

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 the schema already documents all seven parameters; per calibration the baseline is 3. The description does add value on the `schedule` field (cron grammar, a worked pattern table, plan-floor constraint) and `timezone` (DST), plus a full example object, but it repeats rather than extends what the schema says about handler/payload/name/project_id.

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?

Opens with a specific verb+resource ("Create a scheduled trigger") and immediately defines what a schedule is (5-field cron, UTC default, IANA timezone). It also names cron_list as the place to read plan policy, so an agent can tell it apart from cron_update/cron_run/cron_list without opening other schemas.

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 concrete usage context: when the schedule is rejected (CRON_SCHEDULE_TOO_FREQUENT), where to read the interval floor (cron_list with project_id), and the note that existing schedules bypass the check. It never explicitly says when NOT to use this tool (e.g. use cron_run for a one-off manual fire), so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources