Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_guild_onboarding

Update a Discord server’s onboarding configuration, including prompts, enabled status, mode, and default channels.

Instructions

Modify Guild Onboarding. [PUT /guilds/{guild_id}/onboarding]

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_onboarding"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNomode
reasonNoReason (shown in the audit log)
enabledNoEnabled
promptsNoprompts
guild_idYesServer (guild) ID
default_channel_idsNodefault channel ids

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 declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered, but the description adds nothing further. The PUT tag hints at replace semantics but never states whether omitted fields are cleared, whether MANAGE_GUILD-level permissions are required, or how the audit-log reason field is applied.

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 short fragments are front-loaded and contain no filler, but the brevity comes from omission rather than discipline. The endpoint tag is the only element that earns its place.

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 six-parameter mutation with open-world behavior, no output schema, and only minimal annotations, so the description carries real explanatory burden. It supplies no semantics for the substantive fields (prompts structure, default_channel_ids behavior, mode values) and no outcome or side-effect information.

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%, so all six parameters (mode, reason, enabled, prompts, guild_id, default_channel_ids) are already documented in the schema. The description adds no meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

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?

"Modify Guild Onboarding" restates the tool name verbatim with no additional specificity, so the only new information is the bracketed endpoint tag [PUT /guilds/{guild_id}/onboarding]. Nothing distinguishes it from sibling modify_guild_onboarding_responses beyond the implicit "onboarding settings vs. onboarding responses" reading an agent must infer from the name alone.

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 at all: no conditions, no prerequisites, and no mention of the closely related siblings (modify_guild_onboarding_responses, get_guild_onboarding). The agent must infer that this touches onboarding configuration rather than member responses purely from the tool name.

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