Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_guild_new_member_welcome

Read-only

Retrieve the new member welcome settings for a Discord server so you can review how incoming members are greeted and adjust onboarding behavior.

Instructions

Get Guild New Member Welcome. [GET /guilds/{guild_id}/new-member-welcome]

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": "get_guild_new_member_welcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID

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=true, destructiveHint=false, and openWorldHint=true, so safety is covered; the description adds nothing beyond the path, such as required permissions (Manage Guild) or whether an unconfigured welcome returns a default/empty object. It does not contradict the annotations, but it contributes no behavioral context.

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?

Very short and front-loaded, which is good, but the first sentence merely repeats the tool name and the second is a bare route string — no sentence adds meaning an agent couldn't get from the name itself. It is under-specified rather than verbose.

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 simple one-parameter read the bar is low, and annotations cover safety, but with no output schema the description should at least indicate what the welcome object contains (e.g., channel, message template, enable flag). Nothing an agent needs in order to interpret the response is present.

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?

Only one parameter, guild_id, and schema coverage is 100% with a clear 'Server (guild) ID' description, so the schema already does this work. The description adds no format or sourcing details beyond the path template, but baseline 3 applies.

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 plus its HTTP route ('GET /guilds/{guild_id}/new-member-welcome'). The GET verb and path imply retrieval of a guild's new-member welcome configuration, but nothing states what that configuration is or how it differs from sibling reads like get_guild_welcome_screen or get_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?

No when-to-use guidance, no prerequisites, and no mention of the obvious alternative modify_guild_new_member_welcome for the write side. The agent must infer usage entirely from the name and endpoint.

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