Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

acknowledge_guild_feature

Marks a guild feature as read or acknowledged for the current user by submitting a read state type and entity ID, clearing unread indicators and notification badges in that server.

Instructions

Acknowledge Guild Feature. [POST /guilds/{guild_id}/ack/{read_state_type}/{entity_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": {
      "guild_id": "<guild_id>",
      "read_state_type": "<read_state_type>",
      "entity_id": "<entity_id>"
    },
    "name": "acknowledge_guild_feature"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNo
guild_idYesServer (guild) ID
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 this is not read-only, is open-world, and is not destructive, so the safety profile is covered. The description adds nothing beyond the raw endpoint path: no statement of what state changes, whether it is idempotent, what the read_state_type values imply for behavior, or what success looks like. For a mutation tool this leaves most behavioral questions open.

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

Conciseness3/5

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

It is two short fragments with zero redundancy and is front-loaded, so nothing needs trimming. However, the brevity stems from under-specification rather than discipline, and a bare endpoint string is weak structure for a description field.

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?

This is a three-required-parameter mutation tool with no output schema and an ambiguous resource name, so the description should explain effect and context. Instead it supplies only the HTTP route, leaving what gets acknowledged and the resulting side effect entirely undocumented.

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 coverage is 75% and the schema already documents guild_id, entity_id, and the read_state_type value mapping, which is the most semantically important detail. The description contributes nothing about parameter meaning beyond echoing the route placeholder order, so it does not exceed the baseline for high schema coverage.

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?

"Acknowledge Guild Feature" essentially restates the tool name, and the bracketed HTTP path only reveals the route shape rather than what acknowledgement means. An agent cannot tell from this whether it marks a read state, clears an item, or registers an event, nor how it differs from acknowledge_user_feature or acknowledge_notification_center_item.

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

Usage Guidelines1/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 any alternative despite several sibling acknowledge_* tools that likely overlap. The reader is left to guess when this guild-scoped read-state acknowledgement applies versus the user-scoped or notification-center variants.

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