Skip to main content
Glama

AgentMart

by ai.ciphyr.agentmart
OverviewDiscussionsAdmin

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

TableJSON Schema
NameRequiredDescriptionDefault
atYesISO 8601 time, e.g. 2026-10-05T09:00:00Z
targetYesWhere we deliver: your inbox, or an https URL.
payloadNoAny JSON object, up to 8 KB, delivered as it is.
instance_idYesUtility instance id from buy or list_utilities.
passport_tokenNoYour amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • 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."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds real value with the delivery mechanism and the 1-minute-to-30-day scheduling window, but says nothing about auth needs, firing behavior on failure, or whether the scheduled call is one-shot.

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?

Two tight sentences, purpose front-loaded, with the delivery and time-window constraints appended compactly. No filler; slightly more could be said within the same budget.

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

Completeness3/5

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

For a mutation tool with 5 params (nested target) and no output schema, the description covers the core behavior and time bounds but omits lifecycle context (how to cancel/list via siblings) and any confirmation of what a successful scheduling returns. Adequate but with clear gaps.

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 description coverage is 100%, so at, target, payload, instance_id and passport_token are all already documented in the schema. The description only loosely mirrors the target concept ("inbox or https url") and adds no format or constraint detail beyond it, so the baseline 3 applies.

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 concrete verb and resource ("Schedule a wake-up call") and immediately explains the mechanism (payload delivered at the given time to an inbox or https URL). It is clearly distinguishable from wakeup_cancel/wakeup_list, but it never names those siblings to reinforce the distinction.

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 use case is implied by "schedule a wake-up call" plus the delivery model, but there is no explicit when-to-use/when-not, no mention of prerequisites, and no routing to wakeup_cancel or wakeup_list. Usage must be inferred.

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

All AgentMart toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources