Runcrate

Change a schedule

update_schedule

DestructiveIdempotent

Change a schedule; only the fields you pass change. Pause with enabled false, resume with enabled true (a recurring schedule resumes from its next time after now; a one-off needs its run_at still in the future, or pass a new run_at). Passing run_at makes it a one-off and passing cron makes it recurring, so pass at most one of them. spec replaces the whole launch: send every field again, env values included (they are write-only), and keep max_runtime_minutes set. Recurring runs must be at least 15 minutes apart. Changing spec or timing (run_at, cron, timezone), or overlap, or resuming, makes the schedule run as you through this sign-in from then on; pausing or renaming does not.

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

Input Schema

Name	Required	Description
`id`	Yes	Schedule ID
`cron`	No	New 5-field cron (makes the schedule recurring)
`name`	No	New schedule name, 1 to 63 characters
`spec`	No	Replaces the whole launch; resend env values. The launch, with the API field names. kind job: command, gpu_type and max_runtime_minutes are required. kind instance: name and max_runtime_minutes are required, plus gpu_type or instance_type_id.
`run_at`	No	New one-off time, ISO 8601 with an offset (makes the schedule a one-off)
`enabled`	No	false pauses, true resumes
`overlap`	No	Recurring only: skip or allow a run while the previous run is still live
`timezone`	No	IANA timezone for cron, e.g. Europe/London
`workspace`	No	Workspace ID (optional: defaults to the authenticated workspace)
`environment`	No	Environment name (optional: defaults to the environment this session acts in)

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 26, 2026
- changedInput schema / properties / spec / properties / gpu_count / description
```
Previous value: -"Number of GPUs (default 1)"New value: +"GPUs on the machine: 1, 2, 4 or 8 (default 1)"
```
- addedInput schema / properties / spec / properties / gpu_count / enum
```
Added value: +[
+  1,
+  2,
+  4,
+  8
+]
```
- removedInput schema / properties / spec / properties / gpu_count / maximum
```
Removed value: -8
```
- removedInput schema / properties / spec / properties / gpu_count / minimum
```
Removed value: -1
```

Changed3 schema fields changedOct 21, 2026

removedInput schema / properties / env

Removed value: -{
-  "description": "Environment name (optional — defaults to main)",
-  "type": "string"
-}

addedInput schema / properties / environment

Added value: +{
+  "description": "Environment name (optional: defaults to the environment this session acts in)",
+  "type": "string"
+}

changedInput schema / properties / workspace / description

Previous value: -"Workspace ID (optional — defaults to authenticated workspace)"New value: +"Workspace ID (optional: defaults to the authenticated workspace)"

First observedOct 20, 2026

TDQS

A4.3/5.0

Behavior5/5

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

The annotations already flag destructive, idempotent, open-world writes, but the description adds behavior those hints cannot convey: spec replaces the entire launch and requires resending write-only env values, max_runtime_minutes must be kept, recurring runs need at least 15 minutes of spacing, and changing timing or resuming re-runs the schedule under the current sign-in. That last point is a genuine side effect an agent would otherwise miss.

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 partial-update rule, and every sentence carries a distinct constraint with no filler. It is a single dense block, though, and the final clause about running 'as you through this sign-in' is syntactically tangled enough to cost a clarity point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter tool with a nested spec object and no output schema, the description covers the risky parts: replace-not-merge behavior on spec, credential re-entry, mutual exclusion of timing fields, and the authorization side effect. An agent can call this correctly without further discovery.

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 schema already documents each parameter and the baseline is 3. The description goes further by explaining cross-parameter constraints the schema cannot express: run_at and cron are mutually exclusive and each flips the schedule's kind, and spec fields must all be resent including env.

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?

Opens with a specific verb and resource ('Change a schedule') and immediately qualifies it with partial-update semantics ('only the fields you pass change'), which separates it cleanly from create_schedule or the resumed-run behavior of run_schedule_now. It stops short of naming a sibling alternative explicitly, so it does not reach the top of the scale.

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 explicit operative conditions rather than generic advice: pause with enabled false, resume with enabled true, pass at most one of run_at or cron. It also states what resuming means for each schedule kind. What it lacks is an explicit statement of when to use delete_schedule or create_schedule instead of editing, which would fully close the loop.

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

All Runcrate 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.