Skip to main content
Glama

Omnara

by com.omnara
OverviewDiscussions(1)Admin

Update cron trigger

crons_update
Destructive

Updates the schedule, message template, or enabled state. The target is immutable; delete the trigger and create a new one to retarget.

Input Schema

NameRequiredDescriptionDefault
cronNoStandard five-field cron expression (minute, hour, day of month, month, day of week). `TZ=`/`CRON_TZ=` prefixes are rejected; set the `timezone` field instead.
nameNoHuman-readable name. Spaces and punctuation are allowed; leading or trailing whitespace and invisible or control characters are not.
orgIDYesOrganization ID (org_...).
targetNoWhat each firing does: type agent sends the message to an existing agent, type profile launches a new agent from a profile, and type integration hands the firing to an integration, such as a new Slack or Discord thread.
enabledNoWhether the trigger fires on schedule; false pauses it.
timezoneNoIANA time zone the schedule is evaluated in.
projectIDYesProject ID (proj_...).
cronTriggerIDYesCron trigger ID (cron_...).
message_templateNoGo text/template rendered on each firing to produce the message sent to the target. The template receives a `trigger` value with `name`, `fired_at`, `last_fired_at`, and `local_date` fields. Timestamps remain UTC; local_date is the scheduled occurrence's ISO date in the schedule timezone. Required for agent and profile targets; omitted for integration targets, which use their own settings. Rendering is capped at 64 KiB of output and one second of wall-clock time, and `printf` width and precision specifiers are capped at 1024; a firing whose template fails to render is recorded in `failure_report` without sending a message.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / cronTriggerID / description
      Added value: +"Cron trigger ID (cron_...)."
    • addedInput schema / properties / enabled / description
      Added value: +"Whether the trigger fires on schedule; false pauses it."
    • addedInput schema / properties / orgID / description
      Added value: +"Organization ID (org_...)."
    • addedInput schema / properties / projectID / description
      Added value: +"Project ID (proj_...)."
    • addedInput schema / properties / target / description
      Added value: +"What each firing does: type agent sends the message to an existing agent, type profile launches a new agent from a profile, and type integration hands the firing to an integration, such as a new Slack or Discord thread."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the mutation risk is known. The description adds genuinely new behavioral context beyond them: the target field is immutable and retargeting requires delete-and-recreate. It does not describe auth/permission requirements or partial-update semantics.

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 tight sentences, no filler, with the primary action front-loaded and the immutability caveat immediately following. Every clause earns its place.

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 mutation tool with no output schema but rich annotations and full schema coverage, the description supplies the key caveat (immutable target) an agent needs before calling. It omits which fields are optional on update and whether omitted fields are preserved, which is a minor gap given the schema documents defaults.

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% with 9 well-documented parameters, so the schema carries the semantic load and a baseline of 3 applies. The description reinforces the target immutability constraint, which is useful, but adds little on the other parameters.

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 gives a specific verb ('Updates') plus the updatable facets ('schedule, message template, or enabled state'), which is enough to distinguish it from crons_create and crons_delete. It is slightly incomplete against the schema, which also permits updating 'name' and 'timezone', but the core purpose is unambiguous.

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?

It explicitly states the when-not case: 'The target is immutable; delete the trigger and create a new one to retarget.' That routes the agent to crons_delete + crons_create for retargeting. It does not spell out prerequisites or when to prefer update over recreating for other fields, so it falls short of a full 5.

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

All Omnara toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources