Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_set_custom_status

Set your Discord custom status text with an optional emoji, plus an auto-expiry in minutes. Clears the status when given an empty text.

Instructions

Set the custom status text and optional emoji.

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": {
      "text": "<text>"
    },
    "name": "discord_set_custom_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesStatus text, empty string clears it
emojiNoUnicode emoji or name:id for a custom emoji
expiresInMinutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and supplies almost none of it. It does not say this mutates the authenticated user's own profile, whether it requires a scope/permission, what happens to an existing status when overwritten, or how expiry behaves.

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?

A single front-loaded sentence with no redundant wording. Its brevity is appropriate structurally, though it leaves useful content unstated rather than being padded.

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

Completeness2/5

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

For a profile-mutating tool with zero annotation coverage, one undescribed parameter, and no output schema, the definition is too thin. An agent cannot tell persistence, reversibility, or expiry semantics from it.

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

Parameters2/5

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

Schema coverage is 67%: text and emoji are documented well in the schema, and the description merely restates them. The one undocumented parameter, expiresInMinutes (bounds 1–43200, no schema description), is ignored entirely, so the description fails to close the exact gap that exists.

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?

"Set the custom status text and optional emoji" gives a specific verb and resource, and the word "custom" does distinguish it from discord_set_status (presence status) among the siblings. It stops short of naming any sibling or scope conditions, so it is clear but not differentiating.

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 when-to-use guidance: nothing says to prefer discord_clear_status for removal, or discord_set_status for online/idle presence. The one routing clue that exists (empty string clears) lives in the parameter schema, not the description.

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