Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_current_user_guild_join_request

Read-only

Retrieve the current user's pending join request for a specific Discord server by guild ID, so you can check membership request status before joining.

Instructions

Get Current User Guild Join Request. [GET /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>"
    },
    "name": "get_current_user_guild_join_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/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 covered by structured data. The description adds nothing beyond the endpoint path — it does not say what happens if no join request exists (empty result vs. error) or whether it reflects a cached/cooldown state, which is the key behavioral question for this call.

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 that brevity comes from restating the name plus a route string rather than from distilled, high-value content. Nothing is wasted, yet little is contributed.

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?

For a simple single-parameter read tool with no output schema, the description should at minimum describe what is returned (a join request object? null when none pending?) since no output schema exists to answer that. It leaves the agent unable to distinguish 'no request' from 'error', which matters for a 'current user' query tool.

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% for the single 'guild_id' parameter, so the schema already fully documents the input and the baseline is 3. The description adds no meaning beyond it, merely echoing the path template.

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 restates the tool name and appends the HTTP route '[GET /guilds/{guild_id}/requests/@me]', which does hint that the request is scoped to the calling user ('@me'). However, it never explicitly contrasts this with the sibling 'get_guild_join_request', so the agent must infer the difference from the name alone rather than from stated scope.

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 prerequisites, and no mention of the closely related siblings such as get_guild_join_request, list_user_guild_join_requests, or acknowledge_guild_join_request. The agent can only guess that this is the 'check my own pending request' variant.

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