Omnara

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.

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": {
      "cronTriggerID": "<cronTriggerID>",
      "orgID": "<orgID>",
      "projectID": "<projectID>"
    },
    "name": "crons_update"
  }
}

Input Schema

Name	Required	Description
`cron`	No	Standard five-field cron expression (minute, hour, day of month, month, day of week). `TZ=`/`CRON_TZ=` prefixes are rejected; set the `timezone` field instead.
`name`	No	Human-readable name. Spaces and punctuation are allowed; leading or trailing whitespace and invisible or control characters are not.
`orgID`	Yes	Organization ID (org_...).
`target`	No	Updates target options. The target type and ID cannot change. Integration settings can change for future occurrences. Omitted delivery_mode preserves the current mode.
`enabled`	No	Whether the trigger fires on schedule; false pauses it.
`timezone`	No	IANA time zone the schedule is evaluated in.
`projectID`	Yes	Project ID (proj_...).
`cronTriggerID`	Yes	Cron trigger ID (cron_...).
`message_template`	No	Go 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.

Changed1 schema field changedNov 3, 2026

changedInput schema / properties / target / description

Previous 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."New value: +"Updates target options. The target type and ID cannot change. Integration settings can change for future occurrences. Omitted delivery_mode preserves the current mode."

Changed5 schema fields changedOct 17, 2026

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."

First observedOct 13, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety posture is covered. The description adds real value by stating that the target is immutable, but it omits partial-update semantics — it never says that omitted fields (name, cron, timezone) are left unchanged, which is the key behavioral question for an update call.

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 short sentences, front-loaded with what changes, followed by the constraint and the workaround. No filler, though the immutable-target fact is also implied by the schema's target description, making it slightly redundant.

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 nine-parameter nested mutation with no output schema, the definition plus the very rich schema and the destructive annotation block cover what an agent needs to act. The remaining gap is explicit partial-update semantics and what the response returns.

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 the cron format, timezone handling, template contract, and integration settings all documented in the schema itself. The description only restates the update surface and the target immutability, adding marginal meaning beyond structured data; baseline 3 applies.

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?

States a specific verb and the mutable facets explicitly ("schedule, message template, or enabled state"), which maps cleanly to cron, message_template, and enabled. The name plus title already distinguish it from crons_create/crons_get/crons_list, but the description doesn't name a sibling to reinforce the boundary.

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 an explicit when-not rule: if you need to change the target, "delete the trigger and create a new one to retarget." That routes the agent away from a misuse of this tool toward crons_delete plus crons_create. No guidance on reading current state via crons_get before updating.

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

All Omnara tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.