Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_guild

Read-only

Retrieve a Discord server's full settings by guild ID, with optional approximate member and presence counts.

Instructions

Get a server's full settings object. [GET /guilds/{guild_id}]

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

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID
with_countsNoInclude approximate member/presence counts

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/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 description adds that the response is a 'full settings object', which is useful return-shape context, but says nothing about permissions required, partial-field behavior, 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 short clauses, front-loaded with the purpose and followed by the endpoint mapping; nothing is wasted. It is perhaps terse to the point of omitting guidance, but there is no filler.

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 two-parameter read tool with full schema coverage and an explicit safety annotation set, the essentials are present. However, with no output schema, the description does not indicate what the 'settings object' contains or what access is needed, which are the main unknowns an agent faces here.

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 coverage is 100%, with both guild_id and with_counts already documented in the schema. The description contributes no additional meaning about either parameter, so the schema does all the work and the baseline 3 applies.

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?

States a specific verb and resource: 'Get a server's full settings object', with the REST endpoint '[GET /guilds/{guild_id}]' pinning down the semantics. The word 'full' implicitly contrasts with partial views like get_guild_preview, but no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: the agent can infer this is the canonical fetch of a guild's complete configuration, but there is no statement of when to prefer it over get_guild_preview or the many narrower get_guild_* siblings, nor of prerequisites such as needing the bot to be in the guild.

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