nc-mcp-server

dismiss_notification

DestructiveIdempotent

Remove a specific notification permanently by providing its numeric ID. Use list_notifications to locate the ID first.

Instructions

Dismiss (permanently delete) a single notification by its ID.

Use list_notifications first to find the notification_id to dismiss.

Args: notification_id: The numeric ID of the notification to dismiss.

Returns: Confirmation message.

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": {
      "notification_id": "<notification_id>"
    },
    "name": "dismiss_notification"
  }
}

Input Schema

Name	Required	Description	Default
`notification_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Sep 21, 2026

TDQS

A4.5/5.0

Behavior4/5

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

While annotations already declare destructiveHint=true, the description adds the term 'permanently delete,' making irreversibility explicit. It also names the confirmation-message return behavior, and it does not contradict any annotation.

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?

The description is compact and front-loaded, with the core behavior stated first and then neatly separated Args and Returns sections. Every sentence serves a purpose, and there is no redundant filler.

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

Completeness5/5

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

For a one-parameter, single-action tool with annotations and an output schema, this description is complete. It explains what the tool does, what input is needed, how to obtain that input, and what result to expect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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. The Args section fully identifies notification_id as 'The numeric ID of the notification to dismiss,' which is sufficient for the single parameter even though 'numeric' mostly restates the integer type.

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

Purpose5/5

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

The description states a specific verb ('Dismiss'), resource ('notification'), and scope ('single... by its ID'). The word 'single' differentiates it from the sibling dismiss_all_notifications without requiring the agent to inspect that tool.

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

Usage Guidelines4/5

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

It gives an explicit precondition: 'Use list_notifications first to find the notification_id to dismiss.' This provides clear context for when the tool should be invoked, though it does not explicitly state when to favor it over dismiss_all_notifications.

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

Deploy Server