AgentMart

Repeat a wake-up call

schedule_create

Repeat a wake-up call on your wake-up-calls plan: every N minutes (at least 5), hourly, daily or weekly at a time in a time zone. Each run comes with an idempotency_key (dedupe on it). A run that fails after every retry is missed 21 to 25 minutes after its time and puts one "missed" message in alert_inbox_instance_id (or the target inbox). Up to 10 per plan.

Input Schema

Name	Required	Description
`name`	No	Your own label.
`repeat`	Yes	When it repeats.
`target`	Yes	Where each run is delivered.
`payload`	No	Any JSON object, up to 8 KB, sent with every run.
`time_zone`	No	IANA time zone, for example Europe/Istanbul. Default UTC.
`instance_id`	Yes	Utility instance id from buy or list_utilities.
`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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 23, 2026

addedInput schema / examples

Added value: +[
+  {
+    "instance_id": "wkp_exampleexampleexample2",
+    "repeat": {
+      "at": "09:00",
+      "type": "daily"
+    },
+    "target": {
+      "type": "url",
+      "url": "https://example.com/wake"
+    }
+  }
+]

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

A4.1/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing operational behavior: an idempotency_key per run for dedupe, retry exhaustion produces a 'missed' message 21-25 minutes after the scheduled time into `alert_inbox_instance_id`, and a hard cap of 10 schedules per plan. What it omits is what the call returns (schedule id / run handle) and what auth is required, though `passport_token` is described in the schema.

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

Conciseness5/5

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

Three dense sentences, front-loaded with what the tool does, then repeat modes, then failure/quota semantics. Nothing is redundant with the title or annotations and no sentence is 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 an 8-parameter nested-schema creation tool with no output schema, the description covers the important behavioral edges (delivery target semantics, failure notification, quota) that an agent cannot derive from the schema. The main gap is the return value and any prerequisite that `instance_id` must come from `buy`/`list_utilities` before scheduling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3, but the description still adds meaning beyond the schema: the 'at least 5' minute floor, the notion that 'every N' schedules derive from the UTC clock, the idempotency_key that is not itself a schema property, and the limit of 10 per plan. That is real semantic value over the field descriptions.

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 a specific action (create a repeating wake-up call on a wake-up-calls plan) and enumerates the repeat modes, so the resource and verb are unambiguous. However it never distinguishes itself from the closely-named siblings `wakeup_schedule`, `schedule_run`, or `schedule_update`, leaving an agent to infer that this is the creation step.

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?

Usage is implied by the verb 'Repeat ... on your wake-up-calls plan' and the 'Up to 10 per plan' quota hints at a creation limit, but there is no explicit when-to-use / when-not-to-use guidance and no routing to the alternative schedule_* or wakeup_* tools. The agent must infer the create-vs-update-vs-run distinction from names alone.

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.

Repeat a wake-up call

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources