Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_guild_widget

Update a Discord server's widget settings by enabling or disabling it and assigning a channel, with an optional audit log reason.

Instructions

Modify Guild Widget. [PATCH /guilds/{guild_id}/widget]

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>"
    },
    "name": "modify_guild_widget"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
enabledNoEnabled
guild_idYesServer (guild) ID
channel_idNo

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 structurally. The description adds only the PATCH route, which weakly signals a partial-update semantics but says nothing about what changes, whether omitted fields reset, or what happens to the generated widget invite.

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?

Two fragments, no filler words, and front-loaded. However, brevity here reflects under-specification rather than disciplined concision — the bracket route notation is the only substantive content.

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 state-mutating tool with four parameters and no output schema, so the description must carry the explanatory load. It does not: no effect description, no return behavior, no note on the audit-log 'reason' parameter's significance, and no differentiation from the read-side widget tools.

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 75% with each parameter documented inline (guild_id, channel_id, enabled, reason), so the schema largely carries parameter meaning. The description adds nothing beyond that, which is acceptable given the coverage but not compensating for the small gap.

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 ('Modify Guild Widget') and appends the HTTP route '[PATCH /guilds/{guild_id}/widget]'. The route adds a small amount of information, but there is no explanation of what aspect of a widget is modified or how this differs from sibling tools like get_guild_widget or get_guild_widget_settings. It is largely a tautology of the name.

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 alternatives. An agent cannot tell from this text when to modify widget settings versus modify the widget itself versus read it first with the get_* siblings.

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