Skip to main content
Glama

Change, pause or resume a repeating wake-up

schedule_update
DestructiveIdempotent

Change a repeating wake-up (the same checks as creating it; fields left out and its history stay), or pause it ("paused": waiting runs are canceled) or resume it ("active": from the next time after now). An unknown schedule_id answers schedule_not_found. To remove it, schedule_delete; to test it, schedule_run.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "status": "paused",
      "instance_id": "wkp_exampleexampleexample2",
      "schedule_id": "wsc_exampleexampleexample2"
    },
    "name": "schedule_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoYour own label, or null.
repeatNoWhen it repeats.
statusNopaused: stop it; active: run it again.
targetNoWhere each run is delivered.
payloadNoNew JSON sent with every run (up to 8 KB).
time_zoneNoNew IANA time zone, for example Europe/Istanbul. Left out: the current one stays.
instance_idYesUtility instance id from buy or list_utilities.
schedule_idYesschedule id (wsc_...) from schedule_create or schedule_list.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.
alert_inbox_instance_idNoOne of your inboxes for missed-run messages, or null for the target inbox.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "instance_id": "wkp_exampleexampleexample2",
      +    "schedule_id": "wsc_exampleexampleexample2",
      +    "status": "paused"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
    • changedInput schema / properties / repeat / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "minutes": {
      -        "description": "Minutes on the UTC clock: an N that divides a day (5, 15, 60, 1440) runs from 00:00 UTC.",
      -        "maximum": 10080,
      -        "minimum": 5,
      -        "type": "integer"
      -      },
      -      "type": {
      -        "const": "every",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "type",
      -      "minutes"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "minute": {
      -        "maximum": 59,
      -        "minimum": 0,
      -        "type": "integer"
      -      },
      -      "type": {
      -        "const": "hourly",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "type",
      -      "minute"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "at": {
      -        "description": "Time of day \"HH:MM\", 24-hour clock, in time_zone.",
      -        "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
      -        "type": "string"
      -      },
      -      "type": {
      -        "const": "daily",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "type",
      -      "at"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "at": {
      -        "description": "Time of day \"HH:MM\", 24-hour clock, in time_zone.",
      -        "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
      -        "type": "string"
      -      },
      -      "days": {
      -        "description": "Weekdays, each once.",
      -        "items": {
      -          "enum": [
      -            "mon",
      -            "tue",
      -            "wed",
      -            "thu",
      -            "fri",
      -            "sat",
      -            "sun"
      -          ],
      -          "type": "string"
      -        },
      -        "maxItems": 7,
      -        "minItems": 1,
      -        "type": "array"
      -      },
      -      "type": {
      -        "const": "weekly",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "type",
      -      "days",
      -      "at"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "minutes": {
      +        "description": "Minutes on the UTC clock: an N that divides a day (5, 15, 60, 1440) runs from 00:00 UTC.",
      +        "maximum": 10080,
      +        "minimum": 5,
      +        "type": "integer"
      +      },
      +      "type": {
      +        "const": "every",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "type",
      +      "minutes"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "minute": {
      +        "description": "Every hour at this minute (0 to 59) of time_zone's clock.",
      +        "maximum": 59,
      +        "minimum": 0,
      +        "type": "integer"
      +      },
      +      "type": {
      +        "const": "hourly",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "type",
      +      "minute"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "at": {
      +        "description": "Time of day \"HH:MM\", 24-hour clock, in time_zone.",
      +        "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
      +        "type": "string"
      +      },
      +      "type": {
      +        "const": "daily",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "type",
      +      "at"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "at": {
      +        "description": "Time of day \"HH:MM\", 24-hour clock, in time_zone.",
      +        "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
      +        "type": "string"
      +      },
      +      "days": {
      +        "description": "Weekdays, each once.",
      +        "items": {
      +          "enum": [
      +            "mon",
      +            "tue",
      +            "wed",
      +            "thu",
      +            "fri",
      +            "sat",
      +            "sun"
      +          ],
      +          "type": "string"
      +        },
      +        "maxItems": 7,
      +        "minItems": 1,
      +        "type": "array"
      +      },
      +      "type": {
      +        "const": "weekly",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "type",
      +      "days",
      +      "at"
      +    ],
      +    "type": "object"
      +  }
      +]
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds real value on top: omitted fields and history are preserved, pausing cancels waiting runs, resuming starts from the next occurrence after now, and an unknown schedule_id returns schedule_not_found. It stops short of covering payload/time_zone replacement effects beyond 'fields left out stay'.

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?

It is front-loaded and every clause carries information, but the main sentence is dense with nested parentheses and inline quoted enum values, which makes it slower to parse than a short bulleted breakdown would be. No wasted sentences, though.

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 10-parameter mutation tool with nested objects and no output schema, the description covers the important behavioral questions: partial-update semantics, pause/resume effects, and the error case. Remaining gaps (auth via passport_token, payload size limits) are handled by the annotated schema, so nothing critical is missing.

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 baseline is 3. The description earns a bump by explaining merge semantics ('fields left out and its history stay') and giving operational meaning to the status enum values that the schema only summarizes as 'stop it' / 'run it again' — specifically that waiting runs are canceled and that resume takes effect from the next time after now.

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?

The description opens with a specific verb+resource ('Change a repeating wake-up') and enumerates the three modes (change, pause, resume) with their triggering fields. It is immediately distinguishable from schedule_delete and schedule_run, which are named explicitly.

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?

It routes the agent away from this tool for the two adjacent intents: 'To remove it, schedule_delete; to test it, schedule_run.' Combined with the pause/resume semantics, the conditions for choosing each path are explicit.

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.