Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

acknowledge_user_feature

Marks a Discord user read-state item as acknowledged by read-state type and entity ID, clearing unread indicators for guild events, notifications, onboarding, or message requests.

Instructions

Acknowledge User Feature. [POST /users/@me/{read_state_type}/{entity_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": {
      "read_state_type": "<read_state_type>",
      "entity_id": "<entity_id>"
    },
    "name": "acknowledge_user_feature"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNo
entity_idYesEntity ID
read_state_typeYesRead state type: 1 guild events, 2 notification center, 3 guild home, 4 guild onboarding question, 5 message requests

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/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; the description adds nothing about what state changes, whether the ack is idempotent, or what auth (the 'token' param) is required. The POST route confirms a mutation, which is consistent with the annotations but not additive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short with no filler, but the brevity comes from under-specification rather than discipline: a bare name fragment plus a bracketed route is not a usable structure for an agent. Nothing is front-loaded because there is essentially no content.

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 three-parameter mutation with no output schema, the schema and annotations together carry most of the burden, so the tool is callable as-is. However, nothing explains what an acknowledgement affects or how this differs from the many other acknowledge_* tools, which is the key missing piece for correct selection.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67% and the schema itself already enumerates read_state_type values (1 guild events through 5 message requests) and describes entity_id. The description contributes only the path template, which implies read_state_type and entity_id are path params, but adds no meaning about entity_id's accepted ID formats or the role of the token parameter.

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

Purpose2/5

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

The description restates the tool name ('Acknowledge User Feature') and appends an HTTP route, which is close to tautology. It never explains what a 'user feature' is or what acknowledging it does, and with siblings like acknowledge_guild_feature, acknowledge_message, and acknowledge_notification_center_item in the catalog, an agent cannot tell from this text which resource this call targets.

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 guidance, no prerequisites, and no mention of when a sibling such as acknowledge_guild_feature or acknowledge_notification_center_item would be the correct choice instead. The only routing signal is the route template, which the agent must reverse-engineer.

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