Skip to main content
Glama
Sign In
Discord MCP

Discord MCP

by RestartFU
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_guild

Read-only

Fetches information about a Discord server (guild) by its ID, including name, members, channels, and settings.

Instructions

Inspect server details.

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_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

The description adds no behavioral detail beyond what the annotations already provide: readOnlyHint is true, destructiveHint is false. 'Inspect' simply mirrors the read-only hint and does not disclose additional behaviors such as what happens for invalid guild IDs, rate limits, or field scope.

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?

The description is only four words and is front-loaded with the core action. It is efficient and free of filler, though it sacrifices informative depth for brevity.

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 one-parameter getter with read-only annotations, the description is minimally adequate. However, with no output schema and no mention of return details, error behavior, or relationship to list_guilds, an agent gets only an incomplete picture.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain guild_id or its format. While the schema's title 'Guild Id' and pattern are somewhat self-explanatory, the description fails to add meaningful parameter semantics beyond that.

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 'Inspect server details' uses a specific verb and resource, clearly indicating a read operation for a single guild/server. The name get_guild and the required guild_id parameter distinguish it from list_guilds and other tools, though it does not explicitly say 'by guild_id'.

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?

The description gives no guidance on when to use this tool versus alternatives like list_guilds, get_channel, or get_member. It only implies use when server details are needed, with no exclusions or explicit routing.

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