Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_invite

Read-only

Retrieve Discord invite details—server, channel, inviter, and optional counts or expiration—without joining the server.

Instructions

Look up an invite (server, channel, inviter, counts) without joining. [GET /invites/{invite_code}]

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": {
      "invite_code": "<invite_code>"
    },
    "name": "get_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
invite_codeYesInvite code or full invite link (discord.gg/xyz)
with_countsNoInclude approximate member/presence counts
with_expirationNoInclude expiration date
guild_scheduled_event_idNoguild scheduled event id (ID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true. The description adds that looking up an invite does not join the server, reinforcing the lack of membership side effects, and it lists the kind of data returned. It does not cover authentication needs or rate limits, but with annotations present this is a solid addition.

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?

The description is a single front-loaded sentence followed by the HTTP endpoint hint, with no unnecessary wording. Every phrase contributes to understanding purpose or distinguishing behavior.

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

Completeness4/5

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

For a simple read-only lookup tool with four parameters, full schema coverage, and annotations covering safety and openness, the description is nearly complete. It mentions the main returned fields but does not detail the response shape; however, no output schema exists, so a brief return-value summary is adequate.

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 description coverage is 100%, so the schema already fully documents all four parameters. The description mentions counts and invite details but adds no parameter-specific syntax or format guidance beyond what the schema provides, so the baseline of 3 is appropriate.

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

Purpose5/5

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

The description states a specific verb and resource ('look up an invite') and lists the information returned (server, channel, inviter, counts). The phrase 'without joining' clearly distinguishes it from the sibling 'accept_invite'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear usage context by saying 'without joining', which implies this is the read-only alternative to joining or accepting an invite. However, it does not explicitly name alternatives or state exclusions, so it falls short of a perfect score.

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