Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_join_guild

Joins a Discord server using an invite code or full URL after explicit confirmation; the account remains in the server until it leaves.

Instructions

Join a server with an invite code. Requires confirm: true; the account stays joined until it leaves.

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": {
      "code": "<code>",
      "confirm": "<confirm>"
    },
    "name": "discord_join_guild"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesInvite code or full URL
confirmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full load. It does disclose the key behavioral trait that membership persists until an explicit leave, which is real value beyond the schema; however it says nothing about failure modes (invalid/expired/revoked invites), permission or rate-limit constraints, or what the call returns.

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, with the confirmation requirement and the persistence consequence following in order of importance. No filler.

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

Completeness3/5

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

For a simple two-parameter mutation with no annotations and no output schema, the definition covers the action and its persistence but omits error conditions and result content, leaving the agent to discover behavior such as already-a-member responses on its own.

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 50%: the 'code' parameter is documented as 'Invite code or full URL' and 'confirm' is a bare const true. The description reinforces that the input is an invite code and that confirm must be true, but it adds no format guidance (e.g. whether a bare code or full discord.gg URL is preferred, max length behavior).

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 with an invite code.' The trailing clause 'until it leaves' implicitly points at the leave counterpart, so an agent can distinguish join from discord_leave_guild, though no sibling is named explicitly.

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?

Usage is implied rather than stated: the description supplies the precondition (a valid invite code) and the required confirm flag, but gives no when-to-use vs alternatives guidance and no exclusions, e.g. what to do if the account is already a member or the invite is expired.

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