Skip to main content
Glama

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. Returns the rule (wsc_...); schedule_run tests it. One call at one time: wakeup_schedule; an email to 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": {
      "repeat": {
        "at": "09:00",
        "type": "daily"
      },
      "target": {
        "url": "https://example.com/wake",
        "type": "url"
      },
      "instance_id": "wkp_exampleexampleexample2"
    },
    "name": "schedule_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoYour own label.
repeatYesWhen it repeats.
targetYesWhere each run is delivered.
payloadNoAny JSON object, up to 8 KB, sent with every run.
time_zoneNoIANA time zone, for example Europe/Istanbul. Default UTC.
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.
alert_inbox_instance_idNoOne of your inboxes for missed-run messages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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"
      +  }
      +]
  2. 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}$"
  3. Added

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare mutation (readOnlyHint=false), open-world delivery (openWorldHint=true) and non-idempotency (idempotentHint=false). The description goes well beyond that: it discloses the retry/missed-run semantics (missed 21–25 minutes after its time), the 'missed' message destination, the 10-per-plan limit, per-run idempotency_key dedupe, and that it returns the wsc_ rule which schedule_run tests. These are genuine operational traits the annotations cannot express.

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-loaded with the core action, then constraints, then alternatives — a sensible order with no filler sentences. It is dense with parenthetical asides, which slightly taxes first-pass readability but each clause carries information.

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 an 8-parameter tool with nested anyOf objects and no output schema, the description still covers recurrence modes, limits, failure behavior, return value, and sibling routing. The only notable omission is any mention of authentication (passport_token vs. app sign-in), which the schema hints at but the description never explains.

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, but the description adds real meaning: the missed-run message falls back to 'the target inbox' when alert_inbox_instance_id is omitted, and it summarizes the repeat grammar and time-zone framing in prose. It stops short of adding format detail beyond the schema, which the schema already handles well.

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 — 'Repeat a wake-up call on your wake-up-calls plan' – and enumerates the recurrence modes (every N minutes, hourly, daily, weekly). It closes with explicit differentiation from wakeup_schedule (one call at one time) and reminder_create (an email to your human), so an agent can place it among siblings without opening schemas.

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?

Names both alternatives and the conditions that select them: 'One call at one time: wakeup_schedule; an email to your human: reminder_create.' It also states the plan cap ('Up to 10 per plan') which bounds when this call will succeed.

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.