Skip to main content
Glama

Schedule a wake-up call

wakeup_schedule

Schedule one wake-up call: at the given time we deliver your payload to your inbox or to an https url, with up to 3 retries. 1 minute to 30 days ahead, before the plan ends. wakeup_cancel takes its id (wak_...). To repeat, use schedule_create; to email your human, reminder_create.

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": {
      "at": "2026-11-02T09:00:00Z",
      "target": {
        "url": "https://example.com/wake",
        "type": "url"
      },
      "instance_id": "wkp_exampleexampleexample2"
    },
    "name": "wakeup_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
atYesISO 8601 time with seconds and Z or an offset like +02:00, 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 you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / at / description
      Previous value: -"ISO 8601 time, e.g. 2026-10-05T09:00:00Z"New value: +"ISO 8601 time with seconds and Z or an offset like +02:00, e.g. 2026-10-05T09:00:00Z"
  2. Changed2 schema fields changed
    • 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."
  3. 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}$"
  4. 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."
  5. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: delivery is a payload POST/email, up to 3 retries, a bounded time window, and a wakeup id returned as wak_.... It does not mention auth specifics (passport_token fallback) or what happens if all retries fail, but with openWorldHint and non-idempotent annotations already present, this is well above the bar.

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: what it does, the constraints, then the routing to alternatives. No filler, and the core action is front-loaded.

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

Completeness5/5

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

For a 5-parameter mutation with a nested target union and no output schema, the description supplies the missing pieces an agent needs: return id shape, retry behavior, time bounds, and sibling routing. Nothing essential to a correct call is absent.

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 still adds meaning by clarifying that the payload is delivered as-is and that the returned wak_ id is consumed by wakeup_cancel, which is not visible in the input schema. It doesn't elaborate on the at/passport_token semantics beyond what the schema already documents.

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?

States a specific verb and resource ("Schedule one wake-up call") plus the delivery mechanism, and explicitly marks it as one-shot by contrasting with schedule_create for repeats. An agent can distinguish it from wakeup_cancel, schedule_create and reminder_create without opening any schema.

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?

Gives explicit routing: use schedule_create to repeat, reminder_create to email the human, and wakeup_cancel takes the returned wak_ id. It also states hard limits (1 minute to 30 days ahead, before the plan ends), so both when-to-use and boundary conditions are covered.

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.