Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_guild_join_request

Read-only

Retrieve details for a specific Discord guild join request using its request ID. Use it to inspect or verify pending membership applications.

Instructions

Get Guild Join Request. [GET /join-requests/{request_id}]

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": {
      "request_id": "<request_id>"
    },
    "name": "get_guild_join_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYesJoin request ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond the route: no mention of required permissions, whether a missing/expired request errors, or what the returned object contains. With annotations carrying the safety burden, a 2 reflects that the description contributes essentially no behavioral context.

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?

Two short clauses, front-loaded with the operation and backed by the endpoint, with zero filler. It is efficient, though that efficiency reflects how little is being said rather than tight editing of substantive content.

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?

This is a simple one-parameter read tool with annotations and no output schema, so the bar is low and the definition is minimally viable. However, it omits any note on when a join request ID is valid or which sibling to use for listing versus acting, which would be cheap to include.

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% with a single documented parameter ("Join request ID"), so the schema fully carries parameter meaning. The description merely echoes the path variable and adds no format, source, or lookup detail beyond it — the baseline 3 for high-coverage schemas.

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 ("Get Guild Join Request") and adds the HTTP route "[GET /join-requests/{request_id}]", which confirms this is a single-resource fetch keyed by request_id rather than a list. That distinguishes it weakly from list_guild_join_requests, but the differentiation comes only from the path, not from any stated scope or verb nuance.

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 to use this versus list_guild_join_requests, get_current_user_guild_join_request, or the action/acknowledge variants in the sibling set. The agent must infer the intended situation entirely from the tool name.

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