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

Set bot presence

set_bot_presence

Change the bot's status dot (online, idle, dnd, invisible) and custom status text so members see accurate availability. Requires the default gateway connection.

Instructions

Change the bot's status dot and custom status text. Needs the gateway connection this server keeps by default.

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": {
      "status": "<status>"
    },
    "name": "set_bot_presence"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYes
activity_textNoCustom status text shown under the bot's name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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"
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish this is a non-read-only, non-destructive mutation, so the description's job is to add behavior. It does add one useful operational fact — the gateway connection maintained by default — but says nothing about persistence, whether 'invisible' makes the bot appear offline to members, or error behavior. Adequate but thin for a state-changing presence tool.

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?

Two short sentences, front-loaded with the action and its effect. The second sentence carries real information but is phrased vaguely ('this server keeps by default'), leaving the reader to infer what happens if it is unavailable.

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 two-parameter tool with no output schema, the description covers the core effect and precondition. It remains incomplete on side effects of the 'invisible' state and on what the caller gets back or how failures surface, which matters for a presence mutation.

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

Parameters4/5

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

Schema coverage is only 50% (only activity_text is documented in-schema), yet the description compensates by explaining what each parameter actually affects: 'status dot' corresponds to status and 'custom status text' to activity_text. That mapping removes ambiguity about what 'status' means here, which the bare enum of online/idle/dnd/invisible does not convey.

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 names a specific verb ('Change') and a specific resource ('the bot's status dot and custom status text'), which maps cleanly onto the two parameters and distinguishes it from profile-editing siblings like update_bot_profile. It stops short of explicitly contrasting itself with any sibling, so it is clear but not maximally differentiated.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative for changing bot identity versus presence. The only contextual hint is the gateway-connection remark, which describes a precondition rather than a selection rule.

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