Skip to main content
Glama

desktop_dismiss_all_notifications

Dismiss all pending desktop notifications at once, optionally filtering by a specific app. Use it to clear notification clutter and silence alerts before inspecting or acting on windows.

Instructions

agent-desktop dismiss-all-notifications: Dismiss all notifications (--app to filter)

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

Input Schema

NameRequiredDescriptionDefault
appNoOnly dismiss notifications from this app

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does not say whether dismissal is permanent or reversible, whether it fails on protected/system notifications, or what the call returns after dismissing a batch.

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?

One compact sentence with the scope front-loaded and the filter noted parenthetically. The repeated tool name at the start is wasted tokens but nothing else is superfluous.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity, zero-required-parameter bulk operation with full schema coverage this is close to sufficient. The remaining gap is behavioral: permanence and failure modes of dismissing everything at once are unstated.

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 100% and the single optional 'app' parameter is already documented as 'Only dismiss notifications from this app'. The parenthetical '(--app to filter)' merely restates it, adding no format or matching semantics.

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 ('Dismiss all notifications') and the 'all' scope distinguishes it from the singular sibling desktop_dismiss_notification, which can be inferred without opening either schema. The CLI-style name prefix is redundant but the intent is unmistakable.

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 only implied: 'dismiss all' versus the sibling's single-notification dismissal, plus an optional app filter, suggests when to pick this one. There is no explicit when-to-use/when-not statement or named alternative.

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