Skip to main content
Glama
deenesjakoruzh
PaSympa

discord-mcp

by PaSympa
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

discord_get_guild_info

Retrieve comprehensive Discord server details including name, member count, channels, roles, and boost status using the guild ID.

Instructions

Get detailed info about a guild: name, member count, channels, roles, boosts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guild_idYes

Implementation Reference

  • src/tools/discovery.ts:57-69 (handler)
    The handler logic for 'discord_get_guild_info' in src/tools/discovery.ts.
    case "discord_get_guild_info": {
  const guild = await (await discord.guilds.fetch(validateId(args.guild_id, "guild_id"))).fetch();
  return {
    content: [{
      type: "text", text: JSON.stringify({
        id: guild.id, name: guild.name, description: guild.description,
        memberCount: guild.memberCount, channelCount: guild.channels.cache.size,
        roleCount: guild.roles.cache.size, boostLevel: guild.premiumTier,
        boostCount: guild.premiumSubscriptionCount, createdAt: guild.createdAt, owner: guild.ownerId,
      }, null, 2),
    }],
  };
}
  • src/tools/discovery.ts:12-20 (schema)
    The tool definition and schema for 'discord_get_guild_info'.
    {
  name: "discord_get_guild_info",
  description: "Get detailed info about a guild: name, member count, channels, roles, boosts.",
  inputSchema: {
    type: "object",
    properties: { guild_id: { type: "string" } },
    required: ["guild_id"],
  },
},

Tool Definition Quality

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 the tool retrieves information ('Get'), implying it's a read-only operation, but doesn't clarify permissions required, rate limits, error conditions, or what happens if the guild ID is invalid. This leaves significant gaps for a tool that likely interacts with external APIs.

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 and lists specific data points without unnecessary words. Every element (verb, resource, details) earns its place, making it easy to parse quickly.

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?

Given the complexity of Discord API interactions, no annotations, and no output schema, the description is incomplete. It doesn't cover authentication needs, rate limiting, error handling, or the structure of returned data (e.g., JSON format). For a tool that fetches detailed guild information, more context is needed to use it 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?

The input schema has 0% description coverage, documenting only the parameter name and type. The description doesn't mention the guild_id parameter at all, failing to explain its purpose, format (e.g., numeric ID), or where to obtain it. However, with only one parameter, the baseline is higher, but the description adds no value beyond the schema.

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 tool's purpose with a specific verb ('Get') and resource ('detailed info about a guild'), listing key data points like name, member count, channels, roles, and boosts. It distinguishes itself from siblings like discord_list_guilds (which likely lists guilds without details) and discord_get_member_info (which focuses on members), but doesn't explicitly contrast with these alternatives.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a guild ID), compare it to siblings like discord_list_guilds or discord_get_server_stats, or specify contexts where it's appropriate. Usage is implied only by the tool's name and description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PaSympa/discord-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server