Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

bulk_acknowledge_notification_center_items

Marks multiple Discord notification center items as acknowledged in bulk using their item IDs, clearing unread notifications.

Instructions

Bulk Acknowledge Notification Center Items. [POST /users/@me/notification-center/items/bulk-ack]

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

Input Schema

NameRequiredDescriptionDefault
item_idsNoitem ids

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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 covered externally. The description's only additional fact is the HTTP route, and it does not say what 'acknowledge' changes, what permissions are required, or whether the change is reversible.

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 short elements, front-loaded with the operation and followed by the endpoint in brackets. Nothing is padded, though the endpoint adds little for an agent that cannot use HTTP paths directly.

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 mutation tool with no output schema and zero required parameters, the description leaves important questions open: what happens with an empty item_ids array, whether all items are acknowledged by default, and what the response contains. The annotations cover safety but not the semantics of the call.

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 there is a single parameter, so the baseline of 3 applies. The description adds no meaning beyond the schema, notably omitting whether item_ids may be omitted (0 required parameters) and what that would mean.

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 text 'Bulk Acknowledge Notification Center Items' names a verb and a resource, so the basic operation is identifiable. However, it is essentially a restatement of the tool name and does not distinguish it from the singular sibling acknowledge_notification_center_item or state any scope limit.

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 guidance on when to use this bulk variant versus the single-item acknowledge tool, nor any stated preconditions. The agent must infer the choice from the tool name alone.

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