Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_guild_widget

Read-only

Retrieves a Discord server's widget JSON by guild ID, providing public member and presence data for display or integration.

Instructions

Get Guild Widget. [GET /guilds/{guild_id}/widget.json]

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_guild_widget"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/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. The only added detail is the raw endpoint path, which hints at the underlying public API but doesn't disclose behavior such as whether the widget must be enabled or what happens when it is disabled.

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?

The text is very short and front-loaded with the operation, but the bracketed HTTP route is terse scaffolding rather than agent-facing explanation. Nothing is wasted, yet almost nothing useful is conveyed either.

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?

There is no output schema, so the description is the only place to say what the widget payload contains or how it differs from widget settings; it does neither. Even for a simple one-parameter read, an agent lacks the context to know what it will receive.

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?

There is a single required parameter with 100% schema description coverage ('Server (guild) ID'), so the schema carries the semantics. The description's path template confirms guild_id placement in the route but adds no further meaning, which matches the baseline for high coverage.

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

Purpose2/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 Widget') and appends the raw HTTP route, which is essentially tautological. It doesn't explain what a guild widget is or what data it exposes (name, presence count, members, invite), so an agent gains no real understanding beyond the name.

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 siblings such as get_guild_widget_settings or modify_guild_widget, nor any note about preconditions (e.g., widget must be enabled). The agent must infer all of this from names alone.

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