Skip to main content
Glama

Change notification settings

notifications_update
Idempotent

Update your own flat notification preferences, including mute flags, push opt-in, and Europe/Berlin quiet hours; omitted fields stay unchanged and only the calling member is affected.

Instructions

Change your own notification settings in this flat: any subset of the notify* flags, pushOptIn and quiet hours; omitted fields stay as they are. Use it to mute areas or set quiet hours; to read current values call notifications_get first. Quiet hours use Europe/Berlin time and are skipped for urgent events. pushOptIn false deletes all your push subscriptions, and true does not subscribe a device (that happens in the app). Invalid quiet hours give quiet_hours_invalid. Sending an empty object changes nothing and answers ok. Affects only the calling member and notifies nobody. Cannot change other members or flat settings (see wg_update).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "notifications_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.
pushOptInNoMaster switch for push notifications on your member. false also deletes all your stored push subscriptions; true alone does not subscribe a device.
notifyChatNoReceive notifications for new chat messages.
notifyChoresNoReceive notifications about chores.
notifyEventsNoReceive notifications about calendar events.
quietEndHourNoHour of day (0-23, Europe/Berlin time) when quiet hours end. null clears it. Pair with quietStartHour.
notifyExpensesNoReceive notifications about expenses, shares and payments.
notifyShoppingNoReceive notifications about the shopping list.
quietStartHourNoHour of day (0-23, Europe/Berlin time) when quiet hours begin. null clears it. Quiet hours are only active when both start and end are set and differ; a start later than the end wraps past midnight.
notifyInventoryNoReceive notifications about the inventory.
notifyRemindersNoReceive reminders that other members send you.
notifyAnnouncementsNoReceive notifications about announcements.
notifyStatementEmailNoReceive the monthly statement email.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv0.1.1
    • addedInput schema / properties / notifyAnnouncements / description
      Added value: +"Receive notifications about announcements."
    • addedInput schema / properties / notifyChat / description
      Added value: +"Receive notifications for new chat messages."
    • addedInput schema / properties / notifyChores / description
      Added value: +"Receive notifications about chores."
    • addedInput schema / properties / notifyEvents / description
      Added value: +"Receive notifications about calendar events."
    • addedInput schema / properties / notifyExpenses / description
      Added value: +"Receive notifications about expenses, shares and payments."
    • addedInput schema / properties / notifyInventory / description
      Added value: +"Receive notifications about the inventory."
    • addedInput schema / properties / notifyReminders / description
      Added value: +"Receive reminders that other members send you."
    • addedInput schema / properties / notifyShopping / description
      Added value: +"Receive notifications about the shopping list."
    • addedInput schema / properties / notifyStatementEmail / description
      Added value: +"Receive the monthly statement email."
    • addedInput schema / properties / pushOptIn / description
      Added value: +"Master switch for push notifications on your member. false also deletes all your stored push subscriptions; true alone does not subscribe a device."
    • addedInput schema / properties / quietEndHour / description
      Added value: +"Hour of day (0-23, Europe/Berlin time) when quiet hours end. null clears it. Pair with quietStartHour."
    • addedInput schema / properties / quietStartHour / description
      Added value: +"Hour of day (0-23, Europe/Berlin time) when quiet hours begin. null clears it. Quiet hours are only active when both start and end are set and differ; a start later than the end wraps past midnight."
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations are thin (readOnlyHint false, idempotentHint true, destructiveHint false), and the description compensates with real behavioral detail: pushOptIn false deletes all push subscriptions while true does not subscribe a device (asymmetry not obvious from annotations), quiet hours are Europe/Berlin and skipped for urgent events, invalid values surface as quiet_hours_invalid, an empty object is a no-op returning ok, and the operation affects only the caller and notifies nobody. The deletion side effect under destructiveHint=false is disclosed rather than hidden, which is exactly what the description should do.

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 the core purpose and the partial-update rule, then layered with side effects, error code, and scope limits — every sentence carries signal. It is dense and runs long, with minor duplication of the pushOptIn semantics that also appear in the schema, but nothing is padding.

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 13-parameter mutation tool with no output schema and minimal annotations, the description covers the missing pieces: opt-in partial updates, side effects, timezone/edge-case rules for quiet hours, an error code, a no-op case, and the blast radius of the change. An agent has enough to call it correctly and predict the outcome.

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 per-field meaning is already documented. The description still adds partial-update semantics not expressible in the schema ('any subset … omitted fields stay as they are', 'empty object changes nothing') and the quiet-hours interaction rules. It slightly repeats pushOptIn behavior already in the schema, keeping it just below the top mark.

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 ('Change your own notification settings in this flat') and enumerates the mutable surface: notify* flags, pushOptIn, quiet hours. It also bounds scope ('your own', 'in this flat') and explicitly disclaims what it cannot touch (other members, flat settings — see wg_update), so an agent can separate it from notifications_get and wg_update without opening either 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 guidance ('use it to mute areas or set quiet hours'), names the read alternative ('to read current values call notifications_get first'), and routes out-of-scope edits to a named sibling (wg_update). Both the when-to-use and when-not-to-use conditions are present.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.