Skip to main content
Glama

Schedule a Personal Reminder to Remind Them Later

schedule_reminder
Destructive

Schedule, list, retrieve or cancel a personal Pushary reminder for the authenticated user. Scheduled reminders can arrive after the agent exits. One-time only; up to 30 days away, 25 pending per user/site. Scheduling requires body and either inMinutes or at with an explicit UTC offset. requestId identifies one schedule across retries. reminderId retrieves its outcome; no arguments lists pending reminders; cancelReminderId cancels a pending reminder. Returns the scheduled time, state and any delivery warning. Delivery respects stop/mute and active membership. Does not schedule agent work or customer campaigns. API reference: https://pushary.com/docs/agents/reference/tools#schedule_reminder

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "schedule_reminder"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoFuture ISO 8601 timestamp with explicit UTC offset or Z, at most 30 days away. Resolve the user's local time and timezone before scheduling; never guess a timezone.
envNo
bodyNoWhat to remind the authenticated user about, at most 180 UTF-16 units after secret redaction (emoji may use two). Omit all fields to list their pending reminders.
titleNo
agentNameNo
inMinutesNoMinutes from the server clock; use for timers and relative reminders.
machineIdNo
requestIdNoUnique ID for this scheduling operation. Reuse it unchanged on retries to return the original reminder, including after it settles.
sessionIdNo
reminderIdNoLook up your reminder, including its final outcome and delivery status, instead of scheduling or cancelling.
cancelReminderIdNoCancel this user's scheduled reminder instead of creating one. Already-dispatching reminders cannot be cancelled.

Output Schema

NameRequiredDescriptionDefault
hintYesWhat the result means and what to do next.
pendingYesThe authenticated user's pending reminders on this site, soonest first.
warningNoPresent when no phone is connected, so the reminder will appear only in the Pushary Mac app.
deliveryNoPush delivery counts for a reminder looked up by reminderId.
reminderNoThe reminder this call scheduled, matched or looked up. Absent when listing, when cancelling, and when reminderId found nothing.
cancelledNoPresent when cancelReminderId was passed. True when a scheduled reminder was cancelled; false when it was not found or already dispatching or final.
duplicateNoTrue when scheduling returned an existing reminder: a retried requestId, or the same reminder scheduled moments earlier.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "cancelled": {
      +      "description": "Present when cancelReminderId was passed. True when a scheduled reminder was cancelled; false when it was not found or already dispatching or final.",
      +      "type": "boolean"
      +    },
      +    "delivery": {
      +      "additionalProperties": {},
      +      "description": "Push delivery counts for a reminder looked up by reminderId.",
      +      "properties": {
      +        "delivered": {
      +          "description": "Pushes with a provider receipt. A receipt is not proof the person read it.",
      +          "type": "number"
      +        },
      +        "failed": {
      +          "description": "Pushes that failed.",
      +          "type": "number"
      +        },
      +        "pending": {
      +          "description": "Pushes not yet handed to a provider.",
      +          "type": "number"
      +        },
      +        "sent": {
      +          "description": "Pushes Expo accepted.",
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "pending",
      +        "sent",
      +        "delivered",
      +        "failed"
      +      ],
      +      "type": "object"
      +    },
      +    "duplicate": {
      +      "description": "True when scheduling returned an existing reminder: a retried requestId, or the same reminder scheduled moments earlier.",
      +      "type": "boolean"
      +    },
      +    "hint": {
      +      "description": "What the result means and what to do next.",
      +      "type": "string"
      +    },
      +    "pending": {
      +      "description": "The authenticated user's pending reminders on this site, soonest first.",
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "body": {
      +            "description": "Reminder text after secret redaction.",
      +            "type": "string"
      +          },
      +          "fireAt": {
      +            "description": "When the reminder is due, as an ISO 8601 UTC timestamp.",
      +            "type": "string"
      +          },
      +          "id": {
      +            "description": "Reminder ID. Pass it as reminderId to read its outcome, or as cancelReminderId to cancel it while it is scheduled.",
      +            "type": "string"
      +          },
      +          "reason": {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ],
      +            "description": "Why the reminder was suppressed or failed, or null."
      +          },
      +          "settledAt": {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ],
      +            "description": "When the reminder reached a final state, or null while it is pending."
      +          },
      +          "status": {
      +            "description": "scheduled and firing are pending. dispatched means it was handed to the delivery path, not that a person saw it. cancelled, suppressed and failed are final.",
      +            "enum": [
      +              "scheduled",
      +              "firing",
      +              "dispatched",
      +              "cancelled",
      +              "suppressed",
      +              "failed"
      +            ],
      +            "type": "string"
      +          },
      +          "title": {
      +            "description": "Title shown on the phone and the Mac app.",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "title",
      +          "body",
      +          "fireAt",
      +          "status",
      +          "reason",
      +          "settledAt"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "reminder": {
      +      "additionalProperties": {},
      +      "description": "The reminder this call scheduled, matched or looked up. Absent when listing, when cancelling, and when reminderId found nothing.",
      +      "properties": {
      +        "body": {
      +          "description": "Reminder text after secret redaction.",
      +          "type": "string"
      +        },
      +        "fireAt": {
      +          "description": "When the reminder is due, as an ISO 8601 UTC timestamp.",
      +          "type": "string"
      +        },
      +        "id": {
      +          "description": "Reminder ID. Pass it as reminderId to read its outcome, or as cancelReminderId to cancel it while it is scheduled.",
      +          "type": "string"
      +        },
      +        "reason": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "description": "Why the reminder was suppressed or failed, or null."
      +        },
      +        "settledAt": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "description": "When the reminder reached a final state, or null while it is pending."
      +        },
      +        "status": {
      +          "description": "scheduled and firing are pending. dispatched means it was handed to the delivery path, not that a person saw it. cancelled, suppressed and failed are final.",
      +          "enum": [
      +            "scheduled",
      +            "firing",
      +            "dispatched",
      +            "cancelled",
      +            "suppressed",
      +            "failed"
      +          ],
      +          "type": "string"
      +        },
      +        "title": {
      +          "description": "Title shown on the phone and the Mac app.",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "id",
      +        "title",
      +        "body",
      +        "fireAt",
      +        "status",
      +        "reason",
      +        "settledAt"
      +      ],
      +      "type": "object"
      +    },
      +    "warning": {
      +      "description": "Present when no phone is connected, so the reminder will appear only in the Pushary Mac app.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "pending",
      +    "hint"
      +  ],
      +  "type": "object"
      +}
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Goes well beyond the annotations: reminders outlive the agent session, delivery respects stop/mute and active membership, already-dispatching reminders cannot be cancelled, and requestId makes retries return the original reminder. Annotations already flag destructiveHint and openWorldHint, so the description is not required to argue destructiveness, and it adds the quota and delivery-warning context those annotations cannot convey.

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 purpose and constraints before mode routing, and every sentence carries substance. The middle section is a dense run-on enumerating parameter-driven modes in one line, which is harder to parse than a short bulleted split would be.

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 multi-mode tool with 11 parameters, the description covers purpose, quotas, timing rules, idempotency via requestId, mode dispatch, delivery caveats, negative scope, and a reference URL; the return shape is carried by the existing output schema, so nothing an agent needs to call it correctly is missing.

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 coverage is 55%, and the description adds genuine cross-parameter meaning the schema cannot express (body plus exactly one of inMinutes/at, explicit UTC offset required, requestId reused across retries). However, env, title, agentName, machineId and sessionId get no explanation anywhere, leaving five parameters semantically opaque.

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 concrete verbs and the resource precisely: schedule/list/retrieve/cancel a personal Pushary reminder for the authenticated user, one-time only, ≤30 days out. Negative scope ('Does not schedule agent work or customer campaigns') further bounds the purpose, though it never explicitly contrasts with the notification-flavored sibling send_notification.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Routes each mode unmistakably: 'reminderId retrieves its outcome; no arguments lists pending reminders; cancelReminderId cancels a pending reminder.' It also states preconditions (requires body and either inMinutes or at with explicit UTC offset) and limits (25 pending per user/site). It stops short of explicit when-not-to-use guidance versus sibling tools.

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.

Resources