Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_guild_widget_settings

Read-only

Retrieve a Discord server's widget settings, including whether the widget is enabled, to configure the server widget display.

Instructions

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

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

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) 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 structurally. The description adds only the HTTP route, which provides a small hint about the underlying API surface but nothing about return shape, permissions, or rate limits.

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 terse fragments with zero wasted words, and the purpose is front-loaded. It leans toward under-specification rather than verbosity, but the structure itself is clean.

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?

For a simple single-parameter read operation with annotations and full schema coverage, the definition is minimally sufficient to invoke the tool correctly. It leaves gaps around what the settings contain and how it differs from the sibling widget tools, but nothing that would cause a wrong call.

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 parameter (guild_id) with 100% schema description coverage ("Server (guild) ID"), so the schema fully documents it. The description adds no additional meaning beyond that, which is the baseline expectation when schema coverage is complete.

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 states the verb and resource ("Get Guild Widget Settings") and adds the underlying route [GET /guilds/{guild_id}/widget], so an agent knows it reads widget configuration for a guild. However, it essentially restates the tool name and gives no differentiation from the sibling get_guild_widget, which sounds nearly identical.

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 call this versus get_guild_widget or modify_guild_widget, and no prerequisites or exclusions are mentioned. The agent must infer the distinction from the 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