discord-mcp

guild_get

Read-onlyIdempotent

Retrieve a Discord server's metadata to display its overview and calculate limits based on boost tier.

Instructions

Purpose: Fetch guild metadata.

When to use: server overview; compute boost-tier-dependent caps.

Returns: {id, name, icon, owner_id, member_count, description, premium_tier, preferred_locale, features}. Structured name and description remain raw server-owner data; the human-readable text response fences them.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`guild_id`	Yes	Guild to fetch

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.28.0Sep 15, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "$schema": "https://json-schema.org/draft/2020-12/schema",
-    "additionalProperties": {},
-    "properties": {
-      "description": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "features": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "icon": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "id": {
-        "description": "Discord guild (server) ID",
-        "pattern": "^\\d{17,20}$",
-        "type": "string"
-      },
-      "member_count": {
-        "maximum": 9007199254740991,
-        "minimum": -9007199254740991,
-        "type": "integer"
-      },
-      "name": {
-        "type": "string"
-      },
-      "owner_id": {
-        "description": "Discord user ID",
-        "pattern": "^\\d{17,20}$",
-        "type": "string"
-      },
-      "preferred_locale": {
-        "type": "string"
-      },
-      "premium_tier": {
-        "maximum": 9007199254740991,
-        "minimum": -9007199254740991,
-        "type": "integer"
-      }
-    },
-    "required": [
-      "id",
-      "name",
-      "icon",
-      "owner_id",
-      "description",
-      "premium_tier",
-      "preferred_locale",
-      "features"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "category": {
-        "enum": [
-          "client",
-          "server"
-        ],
-        "type": "string"
-      },
-      "code": {
-        "type": "string"
-      },
-      "recovery_hint": {
-        "type": "string"
-      },
-      "retriable": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "code",
-      "retriable",
-      "category",
-      "recovery_hint"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "$schema": "https://json-schema.org/draft/2020-12/schema",
+    "additionalProperties": {},
+    "properties": {
+      "description": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "features": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "icon": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Discord guild (server) ID",
+        "pattern": "^\\d{17,20}$",
+        "type": "string"
+      },
+      "member_count": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "name": {
+        "type": "string"
+      },
+      "owner_id": {
+        "description": "Discord user ID",
+        "pattern": "^\\d{17,20}$",
+        "type": "string"
+      },
+      "preferred_locale": {
+        "type": "string"
+      },
+      "premium_tier": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "icon",
+      "owner_id",
+      "description",
+      "premium_tier",
+      "preferred_locale",
+      "features"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "category": {
+        "enum": [
+          "client",
+          "server"
+        ],
+        "type": "string"
+      },
+      "code": {
+        "type": "string"
+      },
+      "recovery_hint": {
+        "type": "string"
+      },
+      "retriable": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "code",
+      "retriable",
+      "category",
+      "recovery_hint"
+    ],
+    "type": "object"
+  }
+]

First observedv0.22.0Aug 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already convey read-only, idempotent, non-destructive behavior, so the description does not need to restate those. It adds valuable output-context details: the exact returned fields and the note that `name` and `description` are raw server-owner data fenced in the human-readable response. This goes beyond the structured schema.

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 tightly structured into three labeled sections: purpose, when to use, and returns. Every sentence earns its place, and the most essential selection guidance is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only tool with one well-specified parameter, an output schema, and strong annotations, the description is complete. It covers what the tool fetches, when to use it, and what the response contains. The sibling list is broad, but the core guild metadata scope is clearly delineated.

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%, and the sole parameter is already documented as 'Guild to fetch' with a regex pattern. The description adds little about the parameter itself, but none is needed because the schema fully captures it. Baseline 3 is appropriate.

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?

The description states a clear verb and resource: 'Fetch guild metadata.' The Returns section enumerates the fields, making it easy to distinguish this tool from siblings like guild_get_widget or guild_get_welcome_screen. Server overview and boost-tier caps are specific enough to signal the tool's core purpose.

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

Usage Guidelines4/5

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

The description explicitly gives when-to-use guidance: 'server overview; compute boost-tier-dependent caps.' It does not name exclusions or direct the agent to alternative tools for related metadata, but the use cases are concrete and adequate for selecting this tool over most siblings.

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

Deploy Server