Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

create_guild_join_request

Submits a request to join a Discord server using the guild ID, required form fields, and a version timestamp.

Instructions

Create Guild Join Request. [PUT /guilds/{guild_id}/requests/@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>",
      "form_fields": "<form_fields>",
      "version": "<version>"
    },
    "name": "create_guild_join_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionYes
guild_idYesServer (guild) ID
form_fieldsYesform fields

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already state readOnlyHint=false and openWorldHint=true, so the mutation/world-touching profile is covered; the description adds only the HTTP path, which restates that. It omits behavior an agent needs: that this creates a pending request rather than joining outright, what 'form_fields' must contain, and that a cooldown may block the call (a sibling get_guild_join_request_cooldown exists, hinting at rate limiting that is never mentioned here).

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 two fragments with no filler, so nothing is wasted, but the brevity comes from under-specification rather than tight writing. The endpoint is placed after the name rather than being used to explain the operation's semantics.

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 three-required-parameter open-world mutation with no output schema and an opaque free-form array parameter, the definition is too thin: it never says what a join request is, what success returns, or what failure modes (cooldown, already pending) exist. The endpoint does at least anchor scope to @me, which is why this is not lower.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, and the one weak spot is the most important parameter: form_fields is documented only as 'form fields', an empty-items array whose shape is undefined. The description contributes nothing about required keys, value types, or what version (ISO8601) is used for, so it fails to compensate for the coverage gap.

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

Purpose3/5

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

The description pairs the verb 'Create' with the resource 'Guild Join Request', which is intelligible, and the bracketed 'PUT /guilds/{guild_id}/requests/@me' confirms it is a self-scoped write against the current user. But it is essentially a restatement of the tool name plus an endpoint string, and it does nothing to distinguish this from siblings such as join_guild, join_server, or action_guild_join_request.

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 guidance on when this should be used instead of join_guild/join_server, nor on prerequisites such as needing a guild whose membership requires approval. The agent must infer the whole selection logic from sibling names, which the prompt explicitly says cannot establish another tool's behavior.

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