Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_set_status

Set Discord presence status, activity, and custom status to control how your account appears online; use the clear-status tool to reset them.

Instructions

Set presence status, activity and custom status. Use discord_clear_status to reset.

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": "discord_set_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
afkNo
urlNoStream URL, required for Streaming activity
statusNoPresence status
activityNoActivity name, for example "in Minecraft"
activityTypeNoActivity verbPlaying

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a mutation but says nothing about required permissions/intents, whether unspecified fields are preserved or reset, whether status persists after disconnect, or rate limits. Only the reset pairing (discord_clear_status) is disclosed.

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 short sentences, action first and the reset alternative second. Nothing redundant or padded.

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?

With five all-optional parameters, a mutation with no annotations and no output schema, the definition should explain defaults and behavior when fields are omitted (e.g., setting status to 'offline'). It covers purpose and reset routing but leaves those operational questions open.

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 80% with enum documentation for status and activityType, so the baseline is 3. The description adds no parameter-level detail and its mention of 'custom status' does not map cleanly onto any documented property, offering no extra clarity.

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 the resources affected (presence status, activity, custom status), which is concrete. It also names a counterpart tool. The only muddiness is the claim to handle 'custom status' while a sibling named discord_set_custom_status exists, leaving overlap unexplained.

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?

Provides one explicit routing rule: use discord_clear_status to reset. That covers the obvious counterpoint case. It does not say when to prefer discord_set_custom_status over this tool, which is the more likely ambiguity given the overlapping scope.

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