Skip to main content
Glama

desktop_dismiss_notification

Dismiss a desktop notification by its 1-based index and optionally verify its app or title first to avoid closing the wrong alert.

Instructions

agent-desktop dismiss-notification: Dismiss a notification by index

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "index": "<index>"
    },
    "name": "desktop_dismiss_notification"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNoRequire the notification at INDEX to be from this app; INDEX is its position in the unfiltered list
indexYes1-based notification index from list-notifications
expected_appNoExpected app name at INDEX; one expected identity field is required
expected_titleNoExpected title at INDEX; one expected identity field is required

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full disclosure burden, yet it says nothing about whether dismissal is permanent or reversible, whether it triggers any action handler, what happens if the index is stale or out of range, or what the tool returns. For a mutation on live desktop state this is a material gap.

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 short sentence with the action front-loaded and no padding. The 'agent-desktop dismiss-notification:' prefix is redundant with the tool name, and the brevity here reflects under-specification rather than disciplined economy.

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

Completeness2/5

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

A four-parameter mutation tool with no annotations and no output schema needs more than a nine-word sentence. Nothing covers failure modes, the relationship between index and the app filter, or what the caller receives on success.

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%, so the parameters are already fully documented, including the 1-based index and the expected_app/expected_title identity guards. The phrase 'by index' only restates what the schema provides and adds no new meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase 'Dismiss a notification by index' names a specific verb and resource, so the basic action is unambiguous. However, it does not distinguish this tool from the sibling desktop_dismiss_all_notifications or explain the single-versus-bulk boundary, leaving the agent to infer the difference from the names alone.

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 when-to-use guidance, no prerequisites, and no named alternative. The description never says the index must first come from desktop_list_notifications, nor when to prefer this over the dismiss-all sibling.

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