Skip to main content
Glama

Read notification settings

notifications_get
Read-onlyIdempotent

Read your own notification settings for a shared flat, including per-area notify flags, quiet hours, and push status, before updating them.

Instructions

Read your own notification settings in this flat: the notify* flags per area (announcements, chores, expenses, shopping, inventory, reminders, chat, events, statement email), quietStartHour/quietEndHour (0-23 or null), pushOptIn and pushConfigured (whether the server can send push at all). Call it before notifications_update to see current values. Settings belong to the calling member only; other members cannot be read or changed. Read-only.

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, and destructiveHint=false. The description adds meaningful behavior beyond annotations: settings belong only to the calling member, other members cannot be read or changed, quiet hours are 0-23 or null, and pushConfigured indicates whether the server can send push at all.

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?

The description is front-loaded with the core action and settings list, then gives the update relationship and member scope. It is mostly efficient, though 'Read-only' repeats the annotations and the long parenthetical slightly lengthens an otherwise concise definition.

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 simple read-only tool with annotations covering safety and no output schema, the description is complete enough. It explains the returned fields, member scoping, and the interaction with notifications_update, so no critical behavior is left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the single wgCode parameter is fully documented in the schema, including omitting it when the account belongs to one flat. The description does not add parameter meaning beyond the schema, so the baseline 3 is appropriate.

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 uses a specific verb and resource: 'Read your own notification settings in this flat.' It enumerates the returned settings and explicitly distinguishes itself from notifications_update, so an agent can identify it without opening the 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?

It explicitly says 'Call it before notifications_update to see current values,' giving a clear use case and relationship to the sibling mutation tool. The member-only scope also clarifies when it applies.

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