AgentMart

Schedule a wake-up call

wakeup_schedule

Schedule a wake-up call: at the given time we deliver your payload to your inbox or to an https url. 1 minute to 30 days ahead.

Input Schema

Name	Required	Description
`at`	Yes	ISO 8601 time, e.g. 2026-10-05T09:00:00Z
`target`	Yes	Where we deliver: your inbox, or an https URL.
`payload`	No	Any JSON object, up to 8 KB, delivered as it is.
`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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026

addedInput schema / examples

Added value: +[
+  {
+    "at": "2026-11-02T09:00:00Z",
+    "instance_id": "wkp_exampleexampleexample2",
+    "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."

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

Changed5 schema fields changedOct 5, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / passport_token / description

Previous value: -"Leave it out when your MCP app signed in to AgentMart (it is refused then). Otherwise your passport bearer token (amp_...) or session token (amp_s_...), only if your client cannot send it as an Authorization header. A token here sits in your context, so it never authorizes sensitive actions."New value: +"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."

addedInput schema / properties / payload / description

Added value: +"Any JSON object, up to 8 KB, delivered as it is."

changedInput schema / properties / target / anyOf

Previous value: -[
-  {
-    "properties": {
-      "inbox_instance_id": {
-        "maxLength": 64,
-        "minLength": 1,
-        "type": "string"
-      },
-      "type": {
-        "const": "inbox",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "inbox_instance_id"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "type": {
-        "const": "url",
-        "type": "string"
-      },
-      "url": {
-        "format": "uri",
-        "maxLength": 2000,
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "url"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "inbox_instance_id": {
+        "description": "One of your webhook inboxes.",
+        "maxLength": 64,
+        "minLength": 1,
+        "type": "string"
+      },
+      "type": {
+        "const": "inbox",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "inbox_instance_id"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "type": {
+        "const": "url",
+        "type": "string"
+      },
+      "url": {
+        "description": "A public https URL we POST to.",
+        "format": "uri",
+        "maxLength": 2000,
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "url"
+    ],
+    "type": "object"
+  }
+]

addedInput schema / properties / target / description

Added value: +"Where we deliver: your inbox, or an https URL."

First observedOct 4, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare this as a non-readonly, open-world, non-idempotent but non-destructive operation. The description adds useful delivery behavior and the 1-minute-to-30-day scheduling constraint, but it does not cover authentication needs, failure behavior, or cancellation implications.

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?

The description is a single compact sentence with the core action and constraints front-loaded. Every phrase contributes useful information without redundancy.

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 scheduling mutation with rich schema coverage and annotations covering safety semantics, the description is largely complete. It could improve by naming cancellation or list siblings, but it covers the essential scheduling behavior and timing constraints.

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 parameters thoroughly. The description adds a meaningful constraint not present in the schema: scheduling is only valid from 1 minute to 30 days ahead.

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 states a specific verb and resource: scheduling a wake-up call. It is clearly distinguishable from sibling tools like wakeup_cancel and wakeup_list by name, though it does not explicitly call out those alternatives.

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 the tool by mentioning the scheduling window (1 minute to 30 days ahead), but it gives no explicit guidance on when to choose this over sibling tools such as reminder_create or schedule_create, nor does it state exclusions.

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.

Schedule a wake-up call

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources