Skip to main content
Glama
synology-mcp
by r03eRt

DSM notifications

get_notifications
Read-only

Retrieve recent DSM desktop notifications (errors, warnings, events like failed backups or disk warnings) to monitor NAS health; filter by level or limit results.

Instructions

Recent notifications from the DSM desktop (the bell): errors, warnings and events such as finished downloads, failed backups, disk warnings or failed certificate renewals. Each has its time, level, event name and parameters. Needs a DSM administrator account.

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": "get_notifications"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNoOnly this level
limitNoMax notifications, newest first (default 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description is not burdened with safety disclosure. It still adds real value beyond them by disclosing the administrator-account requirement and the shape of each entry (time, level, event name, parameters), which an agent needs before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each doing distinct work: identity of the resource, concrete event examples, return shape, and the auth prerequisite. Front-loaded with the resource and no filler.

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 read-only lister with a fully documented 2-param schema and no output schema, the description covers what the tool returns, what its entries contain, and the auth prerequisite. A note on ordering/recency window is handled by the schema's 'newest first' default, so nothing material is missing.

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% — both 'level' (enum info/warning/error) and 'limit' (1-200, default 30, newest first) are fully documented in the schema. The description adds no filtering or pagination detail beyond that, so the baseline 3 applies.

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?

The description names a specific resource ('Recent notifications from the DSM desktop (the bell)') and enumerates concrete event types (finished downloads, failed backups, disk warnings, certificate renewals), which lets an agent distinguish it from log/health siblings such as get_system_logs. It does not explicitly name a sibling to contrast with, so it stops short of a 5.

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?

Usage is implied by the event catalogue and the stated prerequisite ('Needs a DSM administrator account'), but there is no explicit when-to-use versus when-to-use-something-else guidance, e.g. no pointer telling the agent to prefer get_system_logs for deeper diagnostics.

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