Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get bot info

get_bot_info
Read-only

Retrieve a connected Discord bot's identity, application details, guild count, enabled gateway intents, and server version; specify a bot by name when multiple are configured.

Instructions

Identity and status of a connected Discord bot: bot user, application, guild count, enabled gateway intents, and the server version. With more than one bot configured, pass bot to pick which (list_servers shows the configured bots). Use run_setup_check for a full health check with fix instructions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_bot_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
botNoWhich bot to act as, by name, when more than one is configured. Omit to use the default bot, or with a server, the bot that handles it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / bot / description
      Previous value: -"Which bot to act as, by name, when more than one is configured. Omit to use the default bot."New value: +"Which bot to act as, by name, when more than one is configured. Omit to use the default bot, or with a server, the bot that handles it."
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. Changed3 schema fields changedv1.2.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / bot
      Added value: +{
+  "description": "Which bot to act as, by name, when more than one is configured. Omit to use the default bot.",
+  "type": "string"
+}
  4. First observedv1.0.2

TDQS

A4.2/5.0
Behavior4/5

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

readOnlyHint=true already establishes the safety profile, so the description's job is to add context — and it does, disclosing what identity/status fields come back and how bot resolution behaves when multiple bots exist. It stops short of mentioning pagination (not relevant here) or error behavior when a named bot doesn't exist.

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?

Two sentences, front-loaded with the resource and its returned fields, then the disambiguation and alternative. Nothing is repeated and every clause carries distinct information.

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

Completeness4/5

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

With no output schema, the description compensates by enumerating the key returned fields, which is the most valuable thing it could do. A read-only, single-optional-parameter tool needs little else; only failure behavior for an unknown bot name is left unstated.

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 the bot parameter's description already explaining default fallback and server-derived selection. The definition adds only a navigation hint (list_servers shows configured bots) rather than new semantics, so it sits at the baseline for well-documented schemas.

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?

Specific verb-plus-resource ('Identity and status of a connected Discord bot') followed by an enumeration of exactly what is returned: bot user, application, guild count, gateway intents, server version. It also distinguishes itself from run_setup_check and list_servers, so an agent can identify the tool without opening the schema.

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 routes the agent: use run_setup_check for a full health check with fix instructions, and list_servers to discover configured bot names. It also states the default-bot condition for omitting the parameter. There is no explicit 'do not use this for X' beyond the health-check pointer, but the alternatives are named clearly.

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