Skip to main content
Glama
Sign In
NexusWindows for Claude

NexusWindows for Claude

by pironjulien
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

notifications

Read-onlyIdempotent

Read recent Windows notification center entries by app, including time and text, without opening anything on screen; security codes are masked.

Instructions

Notifications shown by Windows (notification center), most recent first: app, time, texts; read without opening anything on screen; security codes masked. app: part of the app name.

Input Schema

NameRequiredDescriptionDefault
appNo
limitNo

Output Schema

NameRequiredDescriptionDefault
notificationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.7.4
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "NotificationRow": {
+      "properties": {
+        "app": {
+          "title": "App",
+          "type": "string"
+        },
+        "arrived": {
+          "description": "ISO 8601 local time",
+          "title": "Arrived",
+          "type": "string"
+        },
+        "texts": {
+          "description": "Security codes masked",
+          "items": {
+            "type": "string"
+          },
+          "title": "Texts",
+          "type": "array"
+        }
+      },
+      "required": [
+        "app",
+        "arrived",
+        "texts"
+      ],
+      "title": "NotificationRow",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "notifications": {
+      "items": {
+        "$ref": "#/$defs/NotificationRow"
+      },
+      "title": "Notifications",
+      "type": "array"
+    }
+  },
+  "required": [
+    "notifications"
+  ],
+  "title": "NotificationsOutput",
+  "type": "object"
+}
  2. First observedv3.3.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare this as read-only, idempotent, non-destructive, and closed-world. Beyond that, the description adds useful behavior: results are ordered most recent first, entries expose app/time/texts, security codes are masked, and no screen interaction is required. It does not explain limit/pagination behavior, but the additions are substantial.

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 compact and front-loaded with the core resource and ordering. The semicolon-separated details are efficient, though the shorthand 'texts' is slightly vague.

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 simple read-only notification listing tool with an output schema and rich annotations, the description covers what is returned, ordering, filtering by app, and privacy masking. The main omission is limit behavior, but overall it is sufficiently complete.

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 description coverage is 0%, so the description must compensate. It does explain the app parameter as 'part of the app name', which is meaningful, but it does not explain the limit parameter beyond the schema's default value of 20.

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 clearly states the resource (Windows notification center notifications), what each entry contains (app, time, texts), and ordering (most recent first). It is distinguishable from screen-interaction siblings by saying it reads without opening anything on screen, though it does not explicitly name an alternative.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus siblings like windows, look, or logs. The phrase 'read without opening anything on screen' hints at a use case, but it does not state when-not-to-use or name alternatives.

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

Deploy Server

Other Tools