Skip to main content
Glama

Schedule a workflow

writ_set_schedule
DestructiveIdempotent

Schedules a saved workflow: every_minutes, or kind='daily'/'weekly' with time (HH:MM) and days. functions + inputs schedule chosen functions of a multi-function API.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "writ_set_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
tzNoIANA timezone.
daysNoWeekdays 1=Mon..7=Sun (weekly).
kindNointerval | daily | weekly.
timeNoHH:MM (daily/weekly).
inputsNo
enabledNo
functionNo
workflowNo
functionsNo
workflow_idNo
every_minutesNoInterval in minutes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / enabled
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / function
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / functions
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / inputs
      Added value: +{
      +  "type": "object"
      +}
    • addedInput schema / properties / workflow
      Added value: +{
      +  "type": "string"
      +}
  2. Changed10 schema fields changed
    • changedInput schema / properties / days / description
      Previous value: -"ISO weekdays for weekly: 1=Mon .. 7=Sun."New value: +"Weekdays 1=Mon..7=Sun (weekly)."
    • removedInput schema / properties / enabled
      Removed value: -{
      -  "description": "Schedule on or off (default on).",
      -  "type": "boolean"
      -}
    • changedInput schema / properties / every_minutes / description
      Previous value: -"Interval schedule: minutes between runs."New value: +"Interval in minutes."
    • removedInput schema / properties / function
      Removed value: -{
      -  "description": "One function name (alias of `functions`); \"\" or \"all\" = the whole workflow.",
      -  "type": "string"
      -}
    • removedInput schema / properties / functions
      Removed value: -{
      -  "description": "Function names a scheduled run calls (from writ_list_workflows / writ_update_workflow). [] or [\"all\"] = the whole workflow. Omitted: current target kept.",
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • removedInput schema / properties / inputs
      Removed value: -{
      -  "description": "Scheduled-run inputs {input_name: value} (text, number, true/false), used over the workflow's saved values for scheduled runs only. {} clears them; omitted keeps them. No secrets: those are workflow secrets or a persona.",
      -  "type": "object"
      -}
    • changedInput schema / properties / kind / description
      Previous value: -"interval | daily | weekly"New value: +"interval | daily | weekly."
    • changedInput schema / properties / time / description
      Previous value: -"HH:MM local time for daily/weekly."New value: +"HH:MM (daily/weekly)."
    • changedInput schema / properties / tz / description
      Previous value: -"IANA timezone for daily/weekly."New value: +"IANA timezone."
    • removedInput schema / properties / workflow
      Removed value: -{
      -  "type": "string"
      -}
  3. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description never explains what is destructive — e.g. whether setting a schedule overwrites an existing one, what happens to in-flight runs, or what permissions are required. Since the annotations set the expectation of a destructive mutation, the description should have clarified replacement semantics and it does not.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is front-loaded and dense with useful configuration detail. The second sentence about 'functions + inputs schedule chosen functions of a multi-function API' is grammatically tangled and does not clearly convey anything an agent can act on.

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

Completeness2/5

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

With 11 loosely documented parameters, zero required fields, no output schema, and a destructive annotation, the description does not say how to identify the workflow being scheduled, whether the parameters are mutually exclusive, or whether calling it again replaces the prior schedule. For a tool of this complexity the entry is too thin.

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 coverage is 45%, and the description compensates for part of that gap by spelling out every_minutes, kind='daily'/'weekly', time in HH:MM, days, plus functions and inputs. However, four fields critical to identifying the target (workflow, workflow_id, function, enabled) and tz are undocumented in both places, so an agent must guess which identifier to supply.

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 opens with a specific verb and resource ('Schedules a saved workflow') and enumerates the scheduling modes, so an agent can tell this is a schedule-creation tool rather than a run/update/monitor tool. It never names a sibling explicitly, and the trailing clause ('functions + inputs schedule chosen functions of a multi-function API') muddies rather than sharpens the purpose.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this over writ_create_automation, writ_create_monitor, or writ_run_workflow, and no prerequisites such as 'the workflow must already be saved and have an ID'. The interval-vs-daily/weekly split is configuration detail, not tool-selection guidance.

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.