Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

create_guild_onboarding_responses

Creates guild onboarding responses to record member answers and seen prompts for a Discord server's onboarding flow.

Instructions

Create Guild Onboarding Responses. [POST /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": "create_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.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 description needs to add what the annotations cannot say. It adds nothing: no word on whether this overwrites prior submissions, whether the caller must be the user in question, what permissions are required, or what happens to unsupplied fields.

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, but the second bracketed sentence repeats the endpoint already derivable from the parameter list and adds no decision-relevant content. Brevity here reflects under-specification rather than disciplined editing.

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?

The tool takes four parameters including two free-form nested objects, has no output schema, and mutates state, yet the description covers none of that. Crucially it fails to distinguish 'create' from the sibling 'modify' variant, which is the main ambiguity an agent would face.

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 the parameters are nominally documented in the schema, and per the rubric that establishes a baseline of 3. The description contributes no additional meaning, and the schema's own descriptions for onboarding_responses / onboarding_prompts_seen / onboarding_responses_seen are tautological, but the description is not penalized below baseline for that.

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 simply restates the tool name ("Create Guild Onboarding Responses") and appends the raw HTTP route, which duplicates information already implied by the guild_id parameter. It does not explain what an onboarding response actually is or how this differs from the sibling modify_guild_onboarding_responses.

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 onboarding enabled on the guild), and no indication of when to prefer this over modify_guild_onboarding_responses. The agent is left to infer everything from the name alone.

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