Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Discord invite

discord_invite_get
Read-onlyIdempotent

Retrieve a Discord invite's live member and online counts, the server behind it, boosts, tag, traits and games from a code. Use it to inspect a community before joining.

Instructions

Get a Discord invite's live member and online counts, the server behind it, its boosts, tag, traits and games. Requires 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": {
      "code": "<code>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "discord_invite_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesRequired. Invite code (a vanity code or a temporary code), 2 to 32 letters, digits, underscores or hyphens. Vanity codes are case-insensitive; temporary codes are case-sensitive.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the meaningful qualifier 'live' for the counts, signaling that figures are real-time and may drift between calls. It says nothing about failure modes (invalid/expired/revoked invites) or any rate limiting, which are the main behavioral risks for an open-world lookup.

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 front-loaded sentence that packs the return payload efficiently; nothing is buried. The trailing 'Requires `code`' is slightly redundant with the schema's required list but is not costly.

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?

With no output schema, the description usefully enumerates what comes back (counts, server, boosts, tag, traits, games), so an agent knows what it can extract. Read-only behavior is covered by annotations and the conversation_id handshake is explained in-schema. The remaining gap is error behavior for expired or private invites.

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 every parameter, including the pattern for `code` and the unusual context/llm_model/conversation_id fields, is fully documented in the schema. The description only repeats the `code` requirement and adds no extra semantics. Baseline 3 applies when the schema does the heavy lifting.

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?

The description gives a specific verb (get) and a precise resource (a Discord invite) and even enumerates the returned data: live member/online counts, the server behind it, boosts, tag, traits and games. That is far more informative than the title. It does not explicitly contrast with near-siblings such as discord_server_get or discord_template_get, so routing relies on the agent recognizing 'invite' as a distinct resource.

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?

The only conditional content is 'Requires `code`', which restates a schema requirement rather than explaining when to call this tool. There is no guidance on when an invite lookup is the right choice versus fetching the server directly, nor any note about what to do with expired or invalid codes.

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