Skip to main content
Glama

Create an alert (legacy)

create_alarm

Create an alarm on the user's iPhone (kept for agents set up before 2026-10). Without fire_at it is a notification now (the app's feed); with fire_at a reminder at that time. type "normal": a quiet notification. type "urgent": an alarm that rings through silent mode and Focus until the user taps Done or Snooze. Use urgent only when the user must not miss it. "Call me", "ring me", "phone me", "wake me" (in any language) means an urgent alarm: now, or at the time they name. Optional color: pick the one that fits (see the color argument), or the one the user asks for. Optional sound (urgent alarms only): omit it for the user's default sound, or pick one that fits (see the sound argument).

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>"
    },
    "name": "create_alarm"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
typeNoDefault normal.
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.
titleYesShort text shown on the alarm.
ends_atNoReminders only: when it ends (ISO 8601, after fire_at).
fire_atNoOnly when the user named a time: a reminder then. ISO 8601 with offset, e.g. 2026-10-23T09:00:00+03:00. Without an offset the user's timezone is used. Omit for a notification now.
locationNoOptional. An address or place; the app offers to open it in Maps. One line.
countdownNoReminders only: show a countdown to fire_at on the phone.

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
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds real behavioral context: without fire_at it posts a notification to the app's feed, with fire_at it becomes a reminder, and an urgent alarm rings through silent mode and Focus until Done or Snooze. It does not address idempotency or what happens if the same alarm is created twice, leaving the idempotentHint=false implication unexplained.

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-loaded with purpose and the timing rule, then descending detail, with line breaks that make each rule scannable. A few sentences are pure pointers to the schema ('see the color argument', 'see the sound argument') and add little beyond what the enums already say.

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 a 10-parameter creation tool with no output schema, the description covers timing, type semantics, and selection guidance for color and sound well enough to call it correctly. It never says what an agent gets back (an alarm identifier, presumably) or how to modify the result afterwards via update_alarm, which would close the remaining gap.

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 baseline is 3, but the description adds decision heuristics beyond the schema's literal definitions — it ties fire_at presence to notification-vs-reminder behavior and maps natural user phrasing to the 'type' enum. It stays silent on ends_at and countdown, deferring entirely 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?

States a specific verb and resource — 'Create an alarm on the user's iPhone' — and immediately frames the scope with the '(legacy)' marker and 'kept for agents set up before 2026-10'. It is clearly distinct from cancel_alarm, list_alarms and update_alarm, but it never names the sibling 'alert' tool that presumably replaces it, so the sibling routing is implied rather than explicit.

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?

Gives strong when-to-use rules for the type dimension: 'Use urgent only when the user must not miss it', plus a phrase-to-intent mapping ('Call me', 'ring me', 'phone me', 'wake me' means urgent, now or at the named time). What is missing is guidance on when to prefer this legacy tool over the 'alert' sibling, which is the main alternative an agent faces.

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.