Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

acknowledge_guild_join_request

Acknowledge a pending Discord server join request by submitting its guild ID and request ID, confirming that the request has been reviewed.

Instructions

Acknowledge Guild Join Request. [POST /guilds/{guild_id}/requests/{request_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": {
      "guild_id": "<guild_id>",
      "request_id": "<request_id>"
    },
    "name": "acknowledge_guild_join_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID
request_idYesJoin request ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/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 agent knows this is a non-destructive external mutation; the description's POST path is consistent with that and confirms the write targets one specific request. It does not explain what state changes (whether the request stays listed, whether the requester is notified, or whether re-acknowledging is idempotent), so it adds little beyond the structured fields.

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 fragments with no filler and the identity of the operation front-loaded. It is not padded, though the second fragment is purely a raw endpoint reference whose value to an agent is marginal.

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 two-parameter, non-destructive write with full schema coverage and no output schema, the definition is minimally sufficient to call correctly. It is incomplete about the effect of the acknowledgement and about any permission requirements, which matters because the tool mutates shared server state.

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%, with both guild_id ('Server (guild) ID') and request_id ('Join request ID') documented, so the schema carries full parameter meaning. The description adds no syntax, format, or sourcing guidance for these IDs, which is the expected baseline when the schema is complete.

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?

"Acknowledge Guild Join Request" names a verb and a resource, but it largely restates the tool name rather than explaining what acknowledging means for a Discord join request (e.g., marking it as seen, clearing it from a pending list). The bracketed POST path confirms the operation targets a single request scoped to a guild, which adds a little precision, yet nothing distinguishes it from siblings such as action_guild_join_request, reset_guild_join_request, or get_guild_join_request.

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 (e.g., needing MANAGE_GUILD-style permissions or being the request owner), and no mention of when a caller should use this instead of action_guild_join_request or bulk_action_guild_join_requests. The only usage signal is the implied semantics of the verb 'acknowledge'.

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