Skip to main content
Glama

Create a routine

create_routine

Create a NEW repeating routine for the user: a named block at a set time with ordered steps, e.g. "Gym routine" at 18:00 with Warm up 10 min and Lift 40 min. Use it for something done regularly as a sequence of steps; use create_task for a one-off or a simple repeating task, and update_routine to change an existing routine, including the built-in morning and evening routines, which always exist. It runs every day from today unless daysOfWeek is given. Returns {ok:true, id, title, hour, minute, durationMin, steps, daysOfWeek}. Refused with ok:false and nothing saved: reserved_title or title_taken (call get_routines first), invalid_args. Preview rule: if this is the second task or routine change within about 90 seconds, nothing is saved and the result is needs_preview with the pending and saved changes - show them to the user and call again with confirm:true only after they agree.

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": {
      "title": "<title>",
      "hour": "<hour>"
    },
    "name": "create_routine"
  }
}

Input Schema

NameRequiredDescriptionDefault
hourYesStart hour, 0-23 in the user's local time, e.g. 18 for 6 pm.
stepsNoOrdered steps, e.g. [{"name":"Warm up","durationMin":10},{"name":"Lift","durationMin":40}]. Optional.
titleYesThe routine's name, unique among the user's routines, e.g. "Gym routine". "Morning Routine" and "Evening Routine" are reserved.
minuteNoStart minute, 0-59 (default 0).
confirmNoSet true ONLY after the user has seen and approved this change in a preview you showed them (needed when a request changes more than one task or routine). Never set it on your own. Default false.
dayTimesNoA different start time on some weekdays; hour/minute stay the usual time. List only the days that differ, e.g. [{"weekday":6,"hour":9}] for 9:00 on Saturdays. Replaces earlier per-day times; [] = one time every day.
daysOfWeekNoWeekdays it runs on, 1=Monday .. 7=Sunday, e.g. [1,2,3,4,5] for weekdays only. Omit (create) or [] (update) for every day.
durationMinNoLength in minutes, 5-180. Default: the sum of the steps, else 30.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare the write/non-destructive/not-idempotent profile; the description goes well beyond by stating the default schedule (every day from today unless daysOfWeek is given), the exact return shape, and the refusal codes (reserved_title, title_taken, invalid_args) with nothing saved. Most valuably it discloses the preview rule — a second change within ~90 seconds returns needs_preview with pending/saved deltas and requires re-calling with confirm:true after user agreement.

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 sibling routing are front-loaded, followed by defaults, return shape, refusals, and the preview rule in a logical order, with no filler sentences. It is a dense single paragraph, though, and the long compound sentences around the preview rule would be easier to scan as separate lines.

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?

Complete for an eight-parameter mutation tool with no output schema: it supplies the return shape, the default scheduling semantics, the error taxonomy, and the confirmation workflow. An agent has everything needed to call it correctly and to recover from each documented refusal.

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 schema already documents all eight parameters; the description's added value is the defaulting behavior for daysOfWeek omitted vs. [] and the fact that the routine starts today, which the schema does not state. It does not elaborate confirm beyond what the schema says, so it sits above the baseline rather than at the top.

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 ("Create a NEW repeating routine") and defines the domain object concretely as "a named block at a set time with ordered steps," complete with a worked example. It explicitly distinguishes itself from create_task (one-off/simple repeating) and update_routine (changes to existing routines, including built-ins), so an agent can route without opening a 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 positive and negative guidance: use this for something done regularly as a sequence of steps, use create_task for a one-off or simple repeating task, and update_routine to change an existing routine. It also names the exact alternative for a foreseeable failure (title_taken → call get_routines first).

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