Skip to main content
Glama

Save ritual

save_ritual
Idempotent

Create a ritual (a recurring habit) or change one: its name, which weekdays it is due (1 Monday to 7 Sunday), how many days a week may be skipped without breaking the streak, notes, colour, icon, the tag it belongs to, its daily reminder time, or archive it (archived: true; it can be brought back the same way). A ritual that does not exist is created when days is given.

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": {
      "ritual": "<ritual>"
    },
    "name": "save_ritual"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoA tag it belongs to, or "" for none.
daysNoWeekdays it is due, 1 = Monday ... 7 = Sunday.
iconNoAn emoji.
nameNoA new name.
colorNoA colour, e.g. #22c55e.
notesNoNotes on the ritual.
ritualYesThe ritual's name or id.
archivedNotrue archives it, false brings it back.
reminderNoDaily reminder time, HH:MM in the user's time zone, or "off".
start_dateNoThe first day, YYYY-MM-DD. Default today.
grace_per_weekNoDays a week it may be missed without breaking the streak.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and readOnlyHint=false; the description adds real value on top by explaining that archiving is reversible ('it can be brought back the same way') and by pinning creation to the 'days' parameter. It leaves unstated what happens when 'ritual' names a non-existent entry and 'days' is omitted, and there is no note on error or permission behavior.

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?

Two sentences, front-loaded with the core action and the field list, ending with the most decision-relevant rule (upsert on 'days'). The middle field enumeration is dense but every item maps to a real parameter, so there is little waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter upsert tool with no output schema, the description covers the mutate/archive/restore surface and the create condition adequately. Gaps are minor: no statement of failure behavior for an unknown ritual without 'days', and no indication of what is returned.

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 description coverage is 100%, so the baseline is 3, but the description adds a cross-parameter rule the schema cannot express: creation is triggered specifically by supplying 'days', and archive/restore is driven by 'archived'. The rest (weekday numbering, grace days, reminder time) mostly mirrors the schema text rather than extending it.

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+resource ('Create a ritual (a recurring habit) or change one') and enumerates exactly which attributes can be set, including archiving. It also states the upsert condition ('A ritual that does not exist is created when days is given'), so an agent can tell this is the definition-management tool rather than the completion tool (mark_ritual) or list_rituals.

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 a clear create-vs-update rule keyed on presence of 'days' and explains how to archive and restore in the same call. It stops short of explicitly naming alternatives (e.g. list_rituals to find an id, mark_ritual for completion) or stating when not to use it, so guidance is strong but not complete.

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