Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

join_server

Join a Discord server by invite link or code, equivalent to clicking an invite; new accounts may need to complete a captcha.

Instructions

Join a server with an invite link or code (same as clicking an invite). New accounts may be asked for a captcha.

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": {
      "invite": "<invite>"
    },
    "name": "join_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
inviteYesdiscord.gg/xyz link or code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the mutation and open-world nature are covered structurally. The description adds one genuinely useful behavioral detail beyond that: new accounts may hit a captcha, signaling a possible failure mode. It says nothing about what happens on an invalid/expired invite or when already a member, so the disclosure is partial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and followed by the caveat; nothing is padded or redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter mutation with annotations and no output schema, the definition covers the essential action plus the captcha caveat. Only minor gaps remain, such as return value shape and already-joined/invalid-invite behavior.

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 coverage is 100% and the single `invite` parameter is already described as "discord.gg/xyz link or code", which the description merely restates. No extra format, normalization, or validation detail is added, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Join a server") plus the mechanism (invite link or code), which is concrete. It does not differentiate from the near-identical sibling join_guild (guild == server in Discord terms), so an agent can't tell from the text which one to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"same as clicking an invite" gives the agent an intuitive model of the operation, which is helpful context. But there is no explicit when-to-use guidance, no explanation of how it differs from join_guild or join_guild_join_request flow, and no prerequisite/auth guidance.

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