mcp-discord

discord_get_guild

Retrieve Discord server details including name, icon, owner, member count, and features by providing the guild ID. Use this tool to inspect server information through the MCP Discord integration.

Instructions

Fetch details for a single guild — name, icon, owner, member count, features, etc.

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

Input Schema

Name	Required	Description	Default
`guild_id`	Yes
`with_counts`	No	Include approximate member/presence counts.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 23, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Fetch details' which implies a read-only operation, but doesn't cover critical aspects like authentication requirements, rate limits, error handling, or response format. This is a significant gap for a tool with potential API constraints.

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?

The description is a single, efficient sentence that front-loads the core purpose ('Fetch details for a single guild') followed by illustrative examples. Every word earns its place with zero redundancy or unnecessary elaboration.

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?

For a tool with 2 parameters, 50% schema coverage, no annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects like authentication, rate limits, or error cases, nor does it explain the return format. This leaves significant gaps for an AI agent to use the tool effectively.

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 50% (only 'with_counts' has a description). The description adds no parameter-specific information beyond what's implied by 'guild' context. It doesn't explain the 'guild_id' parameter or provide examples, leaving half the parameters undocumented. Baseline 3 is appropriate as the schema covers some ground but description adds minimal value.

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 clearly states the verb 'Fetch' and resource 'details for a single guild', with examples like name, icon, owner, etc. It distinguishes from siblings like discord_list_guilds (which lists multiple guilds) by specifying 'a single guild', but doesn't explicitly contrast with other fetch tools like discord_get_channel or discord_get_member.

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?

No explicit guidance on when to use this tool versus alternatives is provided. It doesn't mention when to choose this over discord_list_guilds for bulk operations or discord_get_member for user-specific data. The description implies usage for retrieving guild details but lacks context about prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.