Skip to main content
Glama

Point a schedule at a newer commit

update_schedule

Repins an existing schedule to a different commit so unattended runs use updated workflow code, preserving its cron, jitter, run history and enabled state.

Instructions

A schedule runs the COMMIT it was created on, not the canvas — so after you change and commit the workflow, the schedule keeps running the old code. This repins it onto another commit (the latest one when versionId is omitted) without touching its cron, jitter, run history or whether it is enabled: no more delete-and-recreate. The auto-save cannot be pinned (commit first). Requires confirm=true: it changes which code runs unattended.

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": {
      "triggerId": "<triggerId>"
    },
    "name": "update_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to repin. Omit/false returns a preview only.
triggerIdYes
versionIdNoThe commit to run. Omit for the workspace's latest commit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations exist, so the description carries the full load and does well: it discloses side effects avoided (cron, jitter, run history, enabled state untouched), the safety gate (confirm=true, otherwise preview only), and why the gate exists ('it changes which code runs unattended'). It stops short of permission/auth requirements or error behavior, which keeps it at 4 rather than 5.

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?

Four short sentences, front-loaded with the conceptual reason before the mechanics, and each sentence contributes (model, action, preserved state, gate). Slightly dense in places — the opening clause is setup rather than instruction — but there is no filler.

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 3-parameter mutation tool with no annotations and no output schema, the definition covers the default-value behavior, the preview-on-omitted-confirm return signal, and the preservation guarantees. Only triggerId identification and permission/error expectations are left implicit.

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?

Adds meaning for two of three parameters: versionId defaults to 'the latest one when omitted' and confirm drives preview-vs-execute. triggerId carries no description in the schema and none in the text, which is the one gap against 67% schema coverage.

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?

States a specific verb and resource ('repins' a schedule onto another commit) and explains the mental model — a schedule runs the commit, not the canvas — so an agent knows exactly what mutation happens. It is clearly distinguishable from create_schedule/delete_schedule because it explicitly frames itself as the alternative to delete-and-recreate.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('after you change and commit the workflow'), names the pattern it replaces ('no more delete-and-recreate'), and states a hard precondition/exclusion ('the auto-save cannot be pinned (commit first)'). The when-to-use condition is fully inferable with no guessing.

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