Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_guild_onboarding

Read-only

Retrieves a Discord server's onboarding configuration, including prompts and default channels, to inspect how new members are guided.

Instructions

Get Guild Onboarding. [GET /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": "get_guild_onboarding"
  }
}

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 the safety profile is fully covered by structured data. The description adds nothing behavioral beyond the raw endpoint path – no note on required permissions, whether onboarding may be unset/unavailable for a guild, or what a missing configuration looks like.

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 bracketed HTTP route is redundant with both the name and the schema's path implication, so one of the two clauses does not earn 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?

With no output schema, the description is the only place an agent could learn what the call returns, and it says nothing about the onboarding payload (prompts, enabled state, default channels). For a tool whose only distinguishing value is its response shape, this leaves a material gap.

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 the schema already documents it at 100% coverage as "Server (guild) ID". The description contributes no additional meaning, which is the expected baseline for a fully documented single-parameter schema.

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?

"Get Guild Onboarding" essentially restates the tool name, and the bracketed HTTP route duplicates it in a different notation. Beyond identifying the resource, the description never explains what onboarding data actually is (a guild-level configuration object), so an agent gets no more than the name already implies.

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 mention of the read/modify pair (modify_guild_onboarding, modify_guild_onboarding_responses) or of the other onboarding-adjacent siblings. The agent must infer from the name alone that this retrieves rather than edits onboarding settings.

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