Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

set_custom_status

Set or clear your Discord custom status text or emoji, optionally scheduling it to expire after a specified number of minutes.

Instructions

Set (or clear) your custom status text/emoji, optionally expiring after N minutes.

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

Input Schema

NameRequiredDescriptionDefault
textNoStatus text; omit both text and emoji to clear
emojiNoUnicode emoji, or custom name:id
expires_in_minutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered; the description adds the valuable non-obvious behaviors that the status can auto-expire after N minutes and that clearing is achieved by omission rather than a dedicated flag. It stops short of stating visibility scope (who sees the status) or what happens on invalid emoji, but that is a modest gap against already-rich annotations.

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?

A single front-loaded sentence that states the action, the clear variant, and the expiry option with zero filler. Every clause carries information the agent needs.

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 zero-required-parameter, non-destructive mutation tool with no output schema, the definition covers action, clearing semantics, and the only undocumented parameter (expiry). Only visibility of the status and error behavior for malformed emoji remain unstated, which is minor at this complexity.

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 67%, with 'expires_in_minutes' carrying no schema description; the description compensates by explaining that expiry is optional and measured in minutes, and it reinforces the clear-by-omission rule for text/emoji. The emoji format ('Unicode emoji, or custom name:id') is only in the schema, which is acceptable.

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 ('Set') and resource ('your custom status text/emoji') with the clear-mode variant parenthetically included, so an agent knows exactly what the tool affects. It does not, however, distinguish itself from the sibling 'set_status' or 'set_voice_channel_status', leaving ambiguity about which status surface this targets.

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: the parenthetical '(or clear)' plus the schema note 'omit both text and emoji to clear' tells the agent how to remove a status, but there is no explicit guidance on when to prefer this over 'set_status' or 'set_voice_channel_status'. No exclusions or preconditions are stated.

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