Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

join_guild

Join a discoverable Discord server by ID, optionally as a lurker without participating.

Instructions

Join a discoverable server by ID (or lurk with lurker=true). [PUT /guilds/{guild_id}/members/@me]

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

Input Schema

NameRequiredDescriptionDefault
lurkerNolurker
guild_idYesServer (guild) ID
locationNolocation
session_idNosession id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, so the mutating, external-facing nature is covered structurally. The description adds value by disclosing the underlying PUT membership endpoint and the discoverability precondition, but says nothing about rate limits, failure modes (e.g., guild full, verification required), or what state results from lurking.

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

Conciseness4/5

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

A single compact sentence with the primary action front-loaded and the alternate mode immediately after it. The trailing bracketed HTTP endpoint is terse but adds a small amount of implementer context rather than padding.

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 4-parameter, open-world mutation with no output schema, the description covers the core action and the lurker flag but leaves two parameters (location, session_id) unexplained and gives no indication of the result of a successful call. Adequate but with clear gaps.

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%, so the schema carries the baseline. The description does add real meaning for lurker by framing it as an alternative to actually joining, but guild_id's 'discoverable' qualifier is the only other addition and location/session_id remain uninterpreted beyond their bare schema labels.

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 discoverable server by ID') plus the qualifying constraint that only discoverable servers qualify. An agent can tell this is a membership-creation action rather than a join-request flow, though it does not explicitly distinguish itself from the similarly named join_server sibling.

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?

The parenthetical '(or lurk with lurker=true)' documents an alternate mode of use, which is genuine guidance. However, there is no statement of prerequisites (e.g., that non-discoverable servers require the join-request tools in the sibling set) or of when to prefer this over join_server.

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