Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

action_guild_join_request

Approve or reject a pending Discord guild join request via PATCH, with optional audit log reason and rejection reason.

Instructions

Action Guild Join Request. [PATCH /guilds/{guild_id}/requests/{request_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>",
      "request_id": "<request_id>",
      "action": "<action>"
    },
    "name": "action_guild_join_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesaction
reasonNoReason (shown in the audit log)
guild_idYesServer (guild) ID
request_idYesJoin request ID
rejection_reasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already state readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered by structure. The description adds nothing beyond the HTTP method, which duplicates the mutation signal already in the annotations. It does not say what the action does (approve vs reject), whether it is reversible, or what permissions are needed.

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 short and front-loaded, with no wasted sentences. But the brevity comes from under-specification rather than efficiency, and the endpoint bracket adds little that the annotations do not already convey.

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 mutation tool with 5 parameters, no output schema, and an undocumented action parameter that almost certainly has an enum of values the agent must know. Given that complexity, the description should explain valid actions, required permissions, and the resulting state change; it supplies none of this.

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 80%, so the schema largely documents the parameters and the baseline of 3 applies. The description contributes no additional meaning for the critical "action" parameter, whose schema entry is only the tautological string "action", and it does not explain the interaction between reason and rejection_reason.

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 is essentially the tool name restated ("Action Guild Join Request") plus a raw endpoint path. "Action" is not a specific verb, and nothing distinguishes this from siblings like acknowledge_guild_join_request or bulk_action_guild_join_requests. The PATCH endpoint implies mutation but the reader still cannot tell what operation is performed on the 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 mention of prerequisites (permissions, pending state), and no routing to alternatives such as the bulk variant or the acknowledge tool. The agent must infer everything from the sibling name list, which the definition itself does not reference.

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