Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_guild_onboarding_responses

Updates a Discord guild's onboarding responses and tracks seen prompts and responses using the server ID and supplied data.

Instructions

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

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

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID
onboarding_responsesNoonboarding responses
onboarding_prompts_seenNoonboarding prompts seen
onboarding_responses_seenNoonboarding responses seen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/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 safety profile is known. The bracketed PUT does add useful behavioral context — full-replacement semantics rather than partial update — but the description says nothing about what state is overwritten, what happens to omitted fields, or auth requirements.

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 very short with no filler sentences, but the brevity comes from under-specification rather than disciplined writing; one of the two fragments is pure name repetition.

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?

For a mutation tool with four parameters, two of them free-form nested objects, and no output schema, the description omits essentially everything an agent needs to call it correctly — what payload shape is expected, what a successful replacement does, and what error conditions exist.

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 every parameter has at least a minimal schema description and the baseline is 3. However, the description adds no meaning beyond the schema, and the nested objects (onboarding_prompts_seen, onboarding_responses_seen) are documented only with restated names, leaving their key/value shape unclear.

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 body of the description is the tool name restated verbatim ("Modify Guild Onboarding Responses"), which is tautological. The bracketed endpoint adds only the fact that this is a PUT on the onboarding-responses sub-resource; it does not differentiate this tool from create_guild_onboarding_responses or modify_guild_onboarding.

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 prerequisite or permission context, and no mention of the closely named siblings such as create_guild_onboarding_responses. The agent must infer entirely from the name whether this creates, replaces, or patches onboarding responses.

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