Skip to main content
Glama

Set a repeating reminder email to my human

reminder_create

Set a repeating reminder email to your own human (daily or weekly at a time in their time zone). Plain words only: no links, code, instructions or requests for secrets. Only to their confirmed address, at most 3 reminder emails a day, each with a one-click stop for them. Up to 5 per plan. Returns the reminder (rem_...) with owner_email: whether email reaches them now. Refused (reminders_stopped_by_owner) while your owner has reminders stopped. To ask them something: ask_human; to wake yourself: wakeup_schedule.

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": {
      "text": "Weekly project check-in.",
      "repeat": {
        "at": "09:00",
        "days": [
          "mon"
        ],
        "type": "weekly"
      },
      "instance_id": "orm_exampleexampleexample2"
    },
    "name": "reminder_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesUp to 500 characters of plain words.
repeatYesDaily or weekly.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "instance_id": "orm_exampleexampleexample2",
      +    "repeat": {
      +      "at": "09:00",
      +      "days": [
      +        "mon"
      +      ],
      +      "type": "weekly"
      +    },
      +    "text": "Weekly project check-in."
      +  }
      +]
    • 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."
  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.7/5.0
Behavior5/5

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

Beyond the annotations, it discloses content policy restrictions, recipient restrictions, send-rate and plan caps, the owner-facing one-click stop, the return identifier shape (rem_...) and the owner_email reachability flag, plus a named refusal condition. For a write tool with no output schema, this is unusually complete behavioral context.

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 primary action is front-loaded, followed by constraints, return behavior, and finally the sibling routing. Every clause carries a distinct operational fact; there is no filler despite the density.

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?

Although there is no output schema, the description explains the returned reminder and the owner_email reachability field, and it covers the refusal case. Combined with fully described parameters, an agent has everything needed to invoke and interpret this tool.

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 the schema already documents instance_id, text, repeat, time_zone and passport_token in detail. The description adds only the recurring framing ('daily or weekly at a time in their time zone'), which mostly restates the repeat/time_zone fields rather than adding new meaning.

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?

The description opens with a specific verb and resource ('Set a repeating reminder email to your own human') and immediately bounds the cadence ('daily or weekly at a time in their time zone'). It is clearly separable from ask_human and wakeup_schedule, which are named and contrasted at the end.

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?

It states when to use it, when to use the alternatives ('To ask them something: ask_human; to wake yourself: wakeup_schedule'), and when it will not work ('Refused (reminders_stopped_by_owner) while your owner has reminders stopped'). Hard limits (3/day, 5 per plan, confirmed address only) further constrain appropriate use.

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.