Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

set_status

Set your Discord presence to online, idle, Do Not Disturb, or invisible by specifying the desired status.

Instructions

Set your online status: online, idle, dnd (Do Not Disturb) or invisible.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare this is a non-read-only, non-destructive, open-world mutation, so safety is covered. The description's added contribution is expanding the cryptic 'dnd' value, though it says nothing about duration, persistence, or reversibility — acceptable for a trivial presence toggle but not rich.

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?

One sentence with the resource and the full value list front-loaded; no filler, no restatement of the tool name beyond what is needed.

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?

For a one-parameter enum tool with annotations and no output schema, the description covers everything required to invoke it correctly. The only gap is a clear boundary against the status-related siblings.

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 0%, but the single enum parameter is self-documenting; the description still adds value by glossing the 'dnd' abbreviation as 'Do Not Disturb'. It adds nothing about persistence, whether the status clears after a timeout, or whether it affects other sessions.

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?

States a specific verb ('Set') and resource ('your online status'), and enumerates the four accepted values inline so the agent knows the full domain immediately. It does not differentiate from close siblings such as set_custom_status or set_voice_channel_status, which likely set a different kind of status, so an agent must infer the distinction.

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

Usage Guidelines3/5

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

Usage is only implied by 'your online status' — it is clear the call affects the caller's own presence, but there is no statement of when to prefer this over set_custom_status, set_voice_channel_status, or set_activity, nor any prerequisite or side-effect guidance.

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