Skip to main content
Glama

cron_update

Idempotent

Update a cron trigger's schedule, IANA timezone, handler, payload, display name, or enabled state. Sending a new schedule or timezone recomputes the next fire and re-checks the plan minimum (see cron_list policy); every other edit, including resuming a paused task, leaves an existing schedule alone.

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": {
      "cron_id": "<cron_id>"
    },
    "name": "cron_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew display name
cron_idYesThe cron ID
enabledNoEnable or disable future fires
handlerNoNew project-relative /api path or full https:// URL the platform will POST to
payloadNoNew JSON object or JSON string passed to the handler
scheduleNoNew 5-field cron expression. Re-checked against the plan floor; omitted, the current schedule is untouched.
timezoneNoNew IANA timezone, e.g. America/Los_Angeles. Changing it recomputes next_run_at; omitted, the current timezone stays.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this is a mutating but non-destructive, idempotent operation, so the description must add beyond that, and it does: changing `schedule` or `timezone` triggers a next-fire recompute and a re-check against the plan minimum, while every other edit including resuming a paused task leaves the existing schedule intact. That is genuinely useful side-effect disclosure that cannot be derived from the annotations or schema. It stops short of describing failure modes (e.g., a schedule that violates the plan floor) or the response payload.

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: the first front-loads what can be changed, the second carries the conditional behavior for the two parameters that have consequences. The parenthetical reference to cron_list `policy` is compact and precise, and no sentence merely restates the title or the schema.

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 mutation tool with complete schema documentation and no output schema, the description covers the essential semantic and behavioral ground, including the plan-minimum constraint the agent must anticipate. The remaining gap is that with no output schema present, the description says nothing about what a successful call returns or how a rejected schedule is reported.

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?

Schema coverage is 100%, so the baseline is 3; the description earns above baseline by explaining that omitting `schedule` or `timezone` preserves current values and by flagging which two parameters carry the recompute/re-validation side effect. That is real semantic value-add over the property descriptions, though it does not explain payload encoding, handler URL constraints, or what happens when `enabled` toggles interact with a schedule already past its floor.

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?

The description uses a specific verb (Update) on a specific resource (a cron trigger) and enumerates the mutable facets: schedule, IANA timezone, handler, payload, display name, enabled state. It is unambiguous about operating on an existing cron by cron_id, which implicitly separates it from cron_create/cron_delete, but it never explicitly names an alternative tool, so it falls just short of full sibling routing.

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?

Usage is implied by the field enumeration and the note that unspecified fields are untouched, so an agent can infer this is the partial-edit tool. There is no explicit when-to-use versus when-not guidance, and no pointer to cron_run for immediate execution or cron_create for new triggers; the only sibling reference (cron_list `policy`) is for lookup, not for choosing between tools.

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