Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Discord server widget

discord_server_widget_get
Read-onlyIdempotent

Fetches a Discord server’s public widget with online member count, voice channels, and invite, using its server ID. Use it to display live server activity or verify public status.

Instructions

Get a Discord server's public widget with its online count, voice channels and invite. Requires serverId.

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": {
      "serverId": "<serverId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "discord_server_widget_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
serverIdYesRequired. Server id, 17 to 20 digits and at most 9223372036854775807, e.g. `267624335836053506`. A server whose owner disabled the widget returns `lookupStatus: restricted`.
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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety is covered structurally. The description contributes the word 'public', signaling only publicly exposed data is returned, but it says nothing about the restricted/failure case (that detail lives in the schema, not the description).

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?

Two sentences, the capability first and the prerequisite second, with zero filler. Nothing could be removed without losing information.

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 fetch with full schema coverage and complete annotations, the description is nearly sufficient, and it usefully previews return fields in place of the absent output schema. It stops short of mentioning the restricted-widget behavior, which would be the one gap an agent might hit at call time.

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 serverId, context, llm_model and conversation_id are all fully documented in the schema itself, including the pattern and the `lookupStatus: restricted` outcome. The description only restates that serverId is required, adding no meaning beyond structured data — baseline 3 applies.

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?

States a specific verb (Get) and a precisely scoped resource (a Discord server's public widget), then enumerates the payload it yields: online count, voice channels and invite. That makes it clearly separable from discord_server_get and the other server-level siblings without needing them opened.

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 usage-like statement is the prerequisite 'Requires serverId', which is already implied by the required-parameter list. It never says when this tool is preferable to discord_server_get or discord_servers_list, and gives no when-not-to-use conditions.

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