Skip to main content
Glama

Change a reminder

update_alarm
DestructiveIdempotent

Change a reminder (or the texts, location, colour, icon or sound of a notification). Pass only the fields to change. Setting fire_at re-arms the reminder (status becomes scheduled), even if it was done or cancelled, and moves ends_at with it. color / icon / location: another one, or null for the default. sound (ringing alerts only): another sound, or null to go back to the user's default sound. ends_at: null removes the end. countdown: true or false.

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": {
      "id": "<id>"
    },
    "name": "update_alarm"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAlarm id from list_alarms.
bodyNoOptional details. Supports line breaks and URLs: line breaks are kept, and links, phone numbers and addresses can be tapped in the app.
iconNoOptional. The icon shown with it in the app, the Live Activity and the widget. Pick the one that fits, or omit it for the default (bell). Icons: bell: anything else (the default); checkmark.circle: a task, job or build finished; exclamationmark.triangle: an error, incident, failure or outage; calendar: a meeting, appointment, deadline or event; sportscourt: sport: a match, a game, a workout; gift: a birthday, anniversary or holiday; cart: shopping, orders, deliveries, prices; airplane: travel: flights, trips, check-in; heart: health and personal life: medication, family, self-care; briefcase: work: reviews, follow-ups, documents, clients; terminal: a terminal or command-line job; hammer: building something: a build, a project; wrench.and.screwdriver: maintenance, repairs, settings; ladybug: a bug or a failing test; server.rack: servers, infrastructure, deploys; cpu: hardware, load, performance; cloud: cloud services, backups, sync; lock: security, access, passwords; key: keys, credentials, certificates; shippingbox: packages, releases, deliveries; doc.text: documents, notes, reports; chart.bar: numbers, stats, dashboards; chart.line.uptrend.xyaxis: growth, prices, markets; flag: a milestone or a goal; star: something important or a favourite; bolt: fast or urgent, power, energy; flame: something hot: a streak, a fire to put out; lightbulb: an idea or a tip; megaphone: an announcement or news; envelope: email and letters; bubble.left: a chat or a reply to send; person.2: people: a meeting, family, friends; house: home and household; car: driving, the car, parking; tram: public transport, commuting; bicycle: cycling; figure.run: running, walking, exercise; dumbbell: the gym, strength training; pills: medication; cross.case: a doctor, first aid, health care; bed.double: sleep, bedtime, a hotel; cup.and.saucer: coffee, tea, a break; fork.knife: meals, cooking, a restaurant; birthday.cake: a birthday; party.popper: a party or a celebration; music.note: music, a concert, practice; film: a film, a show, video; book: reading, studying, a book; graduationcap: school, classes, exams; pawprint: pets, the vet, walking the dog; leaf: plants, the garden, nature; sun.max: sunny weather, outdoors, the morning; moon: the evening or night; umbrella: rain, the weather; creditcard: payments, cards, subscriptions; banknote: money, bills, salary; bag: shopping, something to pack; gamecontroller: games, gaming; camera: photos, a camera; suitcase: packing, luggage, a trip.
typeNo
colorNoOptional. The colour in the app (its icon in the feed and the list, the alarm screen and the Live Activity). Use the colour the user asks for. Otherwise pick the one that fits best, or omit it for the default (blue). Colours: blue: everything else (the default); red: critical: incidents, outages, failures, hard deadlines; orange: important or due soon: reviews, renewals, follow-ups; green: personal and health: sport, medication, family errands, money; purple: events and fun: meetings, birthdays, trips, matches; teal: calm and technical: builds, servers, routine jobs; pink: love and care: partner, kids, gifts; yellow: heads-up: warnings that are not urgent, sunny plans; indigo: night and focus: sleep, deep work, quiet time; mint: fresh starts: habits, water, cleaning; cyan: travel and outdoors: flights, weather, the sea; brown: home and food: cooking, coffee, chores; gray: low priority: someday, notes, background tasks; graphite: admin: paperwork, taxes, bills; lime: energy: workouts, runs, games; coral: social: friends, parties, calls to make.
soundNoOptional. The sound it rings with: only when it rings (urgent, ring: true); a quiet one is a notification with the sound from the app's Settings. Use the sound the user asks for. Otherwise omit it for the user's chosen default sound (picked in the app's Settings), or pick one when the context clearly suggests it: a football match -> stadium, something that must wake the user -> loudalarm or urgentpulse, a gentle nudge -> calmpiano or softbells. Sounds, calm to loud: default: the iPhone's standard system alarm sound, familiar; calmpiano: calm soft piano, gentle: quiet nudges, evenings; softbells: soft bells, gentle and quiet: a reminder that must not startle; sunrise: slowly rising warm tones: a gentle wake-up in the morning; chime: a clear short chime, neutral: everyday reminders; brightmarimba: bright cheerful marimba, the classic phone alarm feel: a normal alarm; upbeatpop: upbeat pop melody, energetic and happy: workouts, fun plans; urgentpulse: fast insistent pulsing beeps, hard to ignore: something urgent, incidents; loudalarm: very loud aggressive alarm that wakes you up: must not be slept through; stadium: football stadium fans chanting with drums and air horns: matches, sports events.
titleNo
ends_atNoReminders only: the new end (ISO 8601, after fire_at), or null for none.
fire_atNoNew time, ISO 8601 with offset (reminders only).
locationNoOptional. An address or place; the app offers to open it in Maps. One line.
countdownNoReminders only: show a countdown to fire_at, or not.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / color / description
      Previous value: -"Optional. The colour in the app (its icon in the feed and the list, the alarm screen and the Live Activity). Use the colour the user asks for. Otherwise pick the one that fits best, or omit it for the default (blue). Colours: blue: everything else (the default); red: critical: incidents, outages, failures, hard deadlines; orange: important or due soon: reviews, renewals, follow-ups; green: personal and health: sport, medication, family errands, money; purple: events and fun: meetings, birthdays, trips, matches."New value: +"Optional. The colour in the app (its icon in the feed and the list, the alarm screen and the Live Activity). Use the colour the user asks for. Otherwise pick the one that fits best, or omit it for the default (blue). Colours: blue: everything else (the default); red: critical: incidents, outages, failures, hard deadlines; orange: important or due soon: reviews, renewals, follow-ups; green: personal and health: sport, medication, family errands, money; purple: events and fun: meetings, birthdays, trips, matches; teal: calm and technical: builds, servers, routine jobs; pink: love and care: partner, kids, gifts; yellow: heads-up: warnings that are not urgent, sunny plans; indigo: night and focus: sleep, deep work, quiet time; mint: fresh starts: habits, water, cleaning; cyan: travel and outdoors: flights, weather, the sea; brown: home and food: cooking, coffee, chores; gray: low priority: someday, notes, background tasks; graphite: admin: paperwork, taxes, bills; lime: energy: workouts, runs, games; coral: social: friends, parties, calls to make."
    • changedInput schema / properties / icon / description
      Previous value: -"Optional. The icon shown with it in the app, the Live Activity and the widget. Pick the one that fits, or omit it for the default (bell). Icons: bell: anything else (the default); checkmark.circle: a task, job or build finished; exclamationmark.triangle: an error, incident, failure or outage; calendar: a meeting, appointment, deadline or event; sportscourt: sport: a match, a game, a workout; gift: a birthday, anniversary or holiday; cart: shopping, orders, deliveries, prices; airplane: travel: flights, trips, check-in; heart: health and personal life: medication, family, self-care; briefcase: work: reviews, follow-ups, documents, clients."New value: +"Optional. The icon shown with it in the app, the Live Activity and the widget. Pick the one that fits, or omit it for the default (bell). Icons: bell: anything else (the default); checkmark.circle: a task, job or build finished; exclamationmark.triangle: an error, incident, failure or outage; calendar: a meeting, appointment, deadline or event; sportscourt: sport: a match, a game, a workout; gift: a birthday, anniversary or holiday; cart: shopping, orders, deliveries, prices; airplane: travel: flights, trips, check-in; heart: health and personal life: medication, family, self-care; briefcase: work: reviews, follow-ups, documents, clients; terminal: a terminal or command-line job; hammer: building something: a build, a project; wrench.and.screwdriver: maintenance, repairs, settings; ladybug: a bug or a failing test; server.rack: servers, infrastructure, deploys; cpu: hardware, load, performance; cloud: cloud services, backups, sync; lock: security, access, passwords; key: keys, credentials, certificates; shippingbox: packages, releases, deliveries; doc.text: documents, notes, reports; chart.bar: numbers, stats, dashboards; chart.line.uptrend.xyaxis: growth, prices, markets; flag: a milestone or a goal; star: something important or a favourite; bolt: fast or urgent, power, energy; flame: something hot: a streak, a fire to put out; lightbulb: an idea or a tip; megaphone: an announcement or news; envelope: email and letters; bubble.left: a chat or a reply to send; person.2: people: a meeting, family, friends; house: home and household; car: driving, the car, parking; tram: public transport, commuting; bicycle: cycling; figure.run: running, walking, exercise; dumbbell: the gym, strength training; pills: medication; cross.case: a doctor, first aid, health care; bed.double: sleep, bedtime, a hotel; cup.and.saucer: coffee, tea, a break; fork.knife: meals, cooking, a restaurant; birthday.cake: a birthday; party.popper: a party or a celebration; music.note: music, a concert, practice; film: a film, a show, video; book: reading, studying, a book; graduationcap: school, classes, exams; pawprint: pets, the vet, walking the dog; leaf: plants, the garden, nature; sun.max: sunny weather, outdoors, the morning; moon: the evening or night; umbrella: rain, the weather; creditcard: payments, cards, subscriptions; banknote: money, bills, salary; bag: shopping, something to pack; gamecontroller: games, gaming; camera: photos, a camera; suitcase: packing, luggage, a trip."
  2. First observed

TDQS

A4/5.0
Behavior5/5

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

Goes well past the annotations by disclosing real side effects: setting fire_at re-arms the reminder (status becomes scheduled) even if it was done or cancelled, and moves ends_at with it. It also spells out null semantics for color/icon/location/sound/ends_at (revert to default vs remove) and restricts sound to ringing alerts, which an agent could not infer from destructiveHint/idempotentHint alone.

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-loads the mutation-rearm behavior in the second sentence and then groups field semantics into compact clauses, with no filler. The telegraphic "color / icon / location: another one, or null for the default" style is dense but parseable; a lead-in for the field list would aid scanning.

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 destructive mutation tool it covers the risky parts (re-arming a completed reminder, moving ends_at, clearing fields) and the schema richly documents the rest of the enums. The one gap is that, without an output schema, it does not say what the update returns (e.g. the updated reminder object).

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?

With schema coverage at 82% the baseline is 3, but the description earns more by adding null semantics the schema does not state: colour/icon/location take another value or null for the default, sound null returns to the user's default sound, ends_at null removes the end, and countdown is a boolean toggle. It leaves type, title, body, and the id → list_alarms link to the schema.

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?

Opens with a specific verb and resource ("Change a reminder") and enumerates the mutable facets (texts, location, colour, icon, sound), so it is clearly a partial-update tool rather than a create/cancel one. It does not explicitly name cancel_alarm or create_alarm as the alternatives, so it stops short of full sibling differentiation.

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

Usage Guidelines3/5

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

"Pass only the fields to change" gives useful patch-style guidance about how to call it, and the per-field notes imply when each is relevant. However, there is no statement of when to prefer this over create_alarm/cancel_alarm, and no prerequisites or preconditions (e.g. ownership) are mentioned.

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.