Skip to main content
Glama

Set up a routine or reminder

create_routine

Set up a routine: something Alexein, this person's assistant, does for them on its own. A morning brief of their day (calendar, important email, weather), a weekly update draft, an alert when a given person or kind of email writes or for their Slack mentions, a reminder - once or repeating - or a scheduled task: a request answered on a schedule from their memory, email, calendar, Slack, GitHub or Linear (kind task, spec {"ask": their words, at most 500 characters, "sources": [...]}). Use it when they ask: "brief me on weekdays at 7:15", "tell me when Sara emails", "remind me to drink water every 30 minutes from 9 to 6", "every Monday at 9 summarise my open PRs".

Schedules repeat as people say them, in local time - never tell them one cannot. {"once": "2026-11-20T15:00"}; days and times, several a day if they like, {"at": "09:00" or ["09:00", "13:00"], "days": [1, 2, 3, 4, 5]} (Monday is 1); every N minutes or hours, optionally between times, {"every": 30, "unit": "minutes", "from": "09:00", "to": "18:00", "days": [1, 2, 3, 4, 5]}; monthly {"monthly": [1], "at": "09:00"} (31 is the last day); yearly {"yearly": "11-14", "at": "09:00"}. Add "until": "YYYY-MM-DD" to end on a date. Watches take null. A reminder repeats at most every 5 minutes, anything else every hour. For a frequent reminder with no hours given, pick sensible ones, such as 9:00-18:00 on weekdays, and say so.

Pick sensible defaults and tell them what you picked; ask at most one question. tz is their time zone, required. It reaches them in the Alexein desktop app, and by email unless it runs more than once a day or they ask for somewhere else. A routine only tells them things: it sends and spends nothing for them, and a task asked to send or post drafts it for them to review. A refusal says why in plain words: fix the call, or tell them. Returns the routine, with its title and when it next runs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "<kind>",
      "spec": "<spec>",
      "tz": "<tz>"
    },
    "name": "create_routine"
  }
}

Input Schema

NameRequiredDescriptionDefault
tzYesTheir IANA time zone, e.g. Asia/Karachi.
kindYesbrief: a daily brief. weekly: a weekly update draft. email_watch: tell them when an email matches. slack_watch: tell them about Slack mentions or words. reminder: once or repeating. task: a request answered on a schedule.
specYes{"kind": the same kind, ...}. brief: place {name, lat, lon}, prefs [str]. weekly: about, prefs. email_watch: from [addresses], domains, words, about, urgent. slack_watch: mentions (bool), words, about, urgent. reminder: text, context. task: ask, sources, prefs.
reachesNoWhere it reaches them; leave out for their usual places.
scheduleNoWhen it runs, local time; null for email_watch and slack_watch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations it discloses real behavioral constraints: routines only inform and 'send and spend nothing', a task asked to send drafts for review, delivery goes to desktop plus email unless it runs more than once a day, and frequency floors (reminders at most every 5 minutes, everything else hourly). It also explains failure behavior — a refusal states why in plain words — which is exactly the context 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?

Purpose and trigger examples are front-loaded, and the schedule-format block is logically grouped. It is long and repeats some of the schema's own field documentation (the spec contents are described twice, in the description and in the schema's spec field), but the density is largely justified by the tool's complexity.

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 five-parameter mutation with no output schema, the description covers what the tool produces ('Returns the routine, with its title and when it next runs'), how to construct every schedule variant, time zone requirements, delivery channels, and refusal handling. 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.

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 earns above that by spelling out the schedule grammar in prose (once, at/days with Monday=1, every N minutes/hours with from/to, monthly with 31 as last day, yearly, optional 'until') and by noting that watches take a null schedule. Much of this restates schema descriptions, which caps it below 5.

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 opening sentence names a specific verb+resource ('Set up a routine') and immediately defines the concept as autonomous assistant behavior, then enumerates the concrete kinds (morning brief, weekly draft, watch, reminder, scheduled task). An agent can distinguish this from skip_routine/list_routines without opening the schema.

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?

It gives explicit, quoted user utterances that should trigger this tool ('brief me on weekdays at 7:15', 'tell me when Sara emails'), plus operational guidance ('ask at most one question', 'never tell them one cannot', pick sensible defaults and say so). It stops short of stating when NOT to use it, e.g. that existing routines are listed rather than created, so it is not a full when/when-not/alternatives statement.

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