Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

dismiss_mention

Destructive

Removes a message from your Discord mentions inbox by message ID, clearing it from your mention list.

Instructions

Remove a message from your mentions inbox. [DELETE /users/@me/mentions/{message_id}]

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": {
      "message_id": "<message_id>"
    },
    "name": "dismiss_mention"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYesMessage ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real value by making clear only the mention-inbox entry is removed, not the underlying message, and by citing the exact endpoint DELETE /users/@me/mentions/{message_id}. It omits reversibility and auth/rate-limit details, which keeps it from a 5.

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?

Two compact segments with zero filler: the behavioral statement is front-loaded and the endpoint reference is a useful technical suffix. Nothing can be trimmed without losing information.

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

Completeness4/5

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

This is a simple one-parameter mutation, annotations carry the destructive/open-world warnings, and no output schema is needed, so the definition is close to complete. A brief note on idempotency (what happens if the mention is already dismissed) would make it fully sufficient.

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?

There is a single required parameter with 100% schema description coverage, so the schema already documents message_id. The description adds no format, type, or sourcing guidance for the ID beyond the endpoint template, which is the expected baseline when the schema does the work.

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?

"Remove a message from your mentions inbox" names a specific verb and a specific resource with a scoped container (mentions inbox), so the agent can distinguish it from destructive siblings like clear_mention_raid_incident or bulk_delete_messages. It stops short of naming an explicit alternative, but the purpose itself is unambiguous.

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

Usage Guidelines3/5

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

The scope phrase "from your mentions inbox" implies when this applies, but there is no explicit when-to-use, when-not-to-use, or pointer to a sibling tool for related operations (e.g. clearing an entire raid incident). Usage must be inferred from the resource 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