Skip to main content
Glama

desktop_notification_action

Clicks a named action button such as Reply or Open on a desktop notification selected by index, verifying the expected app or title to target the right alert.

Instructions

agent-desktop notification-action: Click an action button on a notification

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>",
      "action": "<action>"
    },
    "name": "desktop_notification_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexYes1-based notification index from list-notifications
actionYesName of the action button to click (e.g., Reply, Open)
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.9/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 behavioral burden and falls short: it does not state whether the notification is dismissed after the click, whether the action can send text, whether it requires an active session or permissions, or what the tool returns. Only the bare mutation (clicking) is disclosed.

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, front-loaded sentence with no filler, though the leading "agent-desktop notification-action:" prefix largely restates the tool name and adds little information beyond the actual behavioral clause.

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?

For a four-parameter, no-annotation, no-output-schema interaction tool, the description is too thin. It omits the identity-safety mechanism implied by expected_app/expected_title, the post-click state of the notification, and the failure behavior when the expected identity does not match.

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 all four parameters including expected_app and expected_title are already documented in the schema. The description adds no extra meaning about parameter format, 1-based indexing, or the identity-verification role of the expected_* fields.

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 verb and object ("Click an action button on a notification"), which a reader can distinguish from siblings like dismiss_notification or list_notifications. It is clear but does not explicitly contrast itself with those siblings beyond the obvious verb difference.

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 or when-not-to-use guidance, and no mention of alternatives such as dismiss_notification or list_notifications. The only implied prerequisite (obtaining the index from a prior listing) appears in the input schema, not the description.

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