Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

acknowledge_notification_center_item

Acknowledges a Discord notification center item by ID, marking it as read and clearing it from the notification center.

Instructions

Acknowledge Notification Center Item. [POST /users/@me/notification-center/items/{item_id}/ack]

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": {
      "item_id": "<item_id>"
    },
    "name": "acknowledge_notification_center_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYesNotification item ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is partly covered and the POST path in the description confirms a mutation. Beyond that the description says nothing about what 'acknowledge' actually does to the item (does it mark it read, clear a badge, hide it?), whether the operation is idempotent, or how an already-deleted or unknown item_id is handled — significant gaps for a state-changing tool.

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?

Two compact elements, front-loaded with the action, with the endpoint serving as a useful disambiguator rather than filler. There is no padding, though the second sentence is a routing detail rather than agent-facing explanation.

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 one-parameter mutation with no output schema, the definition is minimally serviceable: the agent knows what to call and with which ID. It is not complete enough to predict the effect of the call or its failure modes, which is the main thing left unexplained.

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?

The single parameter has 100% schema description coverage ('Notification item ID'), so the schema already carries the semantics and the description adds nothing further about format or source. Baseline 3 applies when the schema does the heavy lifting.

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 pairs a specific verb ('Acknowledge') with a specific resource ('Notification Center Item') and even names the underlying endpoint, so an agent knows exactly which object is being acted on. It stops short of differentiating itself from the sibling bulk_acknowledge_notification_center_items, but the singular scope is legible from the name.

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 when-to-use or when-not-to-use guidance, and no mention of the obvious alternative (bulk_acknowledge_notification_center_items) or of when deleting an item is preferable. The only usage signal is implied by the tool name itself.

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