AgentMart

Change, pause or resume a repeating wake-up

schedule_update

DestructiveIdempotent

Change a repeating wake-up (repeat, time_zone, target, payload, alert inbox, name: the same checks as creating it; its history stays), or pause it ("paused": waiting runs are canceled) or resume it ("active": from the next time after now).

Input Schema

Name	Required	Description
`name`	No	Your own label, or null.
`repeat`	No	When it repeats.
`status`	No	paused: stop it; active: run it again.
`target`	No	Where each run is delivered.
`payload`	No	New JSON sent with every run (up to 8 KB).
`time_zone`	No	New IANA time zone, for example Europe/Istanbul. Left out: the current one stays.
`instance_id`	Yes	Utility instance id from buy or list_utilities.
`schedule_id`	Yes	schedule id (wsc_...) from schedule_create or schedule_list.
`passport_token`	No	Your amp_ token, only if you have no app sign-in and cannot send a header.
`alert_inbox_instance_id`	No	One of your inboxes for missed-run messages, or null for the target inbox.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 23, 2026

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"
+  }
+]

Changed4 schema fields changedOct 13, 2026

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}$"
```

AddedOct 5, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare the mutation/destructive profile. The description adds useful behavior: existing history is retained, pausing cancels waiting runs, and resuming starts from the next time after now. It does not cover auth or rate-limit behavior, but the added context is substantial.

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-loads the three main operations and packs key constraints into one dense sentence. Parentheticals make it slightly hard to scan, but nearly every phrase carries useful meaning and nothing is 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?

Given 10 parameters, nested objects, and no output schema, the description covers the main mutation modes and important side effects. It does not explicitly state partial-update behavior for every field, but combined with the rich schema it is largely complete for correct invocation.

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 description coverage is 100%, so the baseline is 3. The description still adds meaning by enumerating the updatable fields and clarifying status semantics beyond the schema's brief 'paused: stop it; active: run it again' (waiting runs canceled; resume from next time after now).

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 specific verbs (change, pause, resume) and the resource (a repeating wake-up), making clear it is distinct from schedule_create, schedule_list, and schedule_delete. It does not explicitly name those sibling tools, but the operation is unambiguous.

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

Usage Guidelines3/5

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

The description implies when to use each mode (update fields, pause, or resume), but gives no explicit guidance on when to choose this tool over schedule_create, schedule_delete, or other scheduling siblings. The intended context is clear enough, but alternatives are not addressed.

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

All AgentMart tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Change, pause or resume a repeating wake-up

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources