Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

set_activity

Display a playing, listening, watching, competing, or streaming activity on your Discord profile; it lasts only while the MCP connection stays active.

Instructions

Show an activity on your profile: Playing / Listening to / Watching / Competing in / Streaming . Lasts while this MCP is connected.

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

Input Schema

NameRequiredDescriptionDefault
urlNoStream URL (twitch/youtube) for streaming
nameYese.g. a game name
typeNoDefault playing
stateNo
detailsNo
start_nowNoShow elapsed time from now
application_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish non-read-only, open-world, non-destructive behavior. The description adds useful lifecycle context that the activity persists while the MCP is connected, but it omits whether it replaces existing activity, permission requirements, and clearing behavior.

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 compact sentences front-load the effect and follow with the key persistence note. The type list is dense but functional, and no wording is wasted.

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 7-parameter presence mutation with no output schema, the description covers purpose and duration but leaves optional parameter meanings and alternative-tool routing unexplained. Annotations and schema descriptions carry much of the rest, but clear gaps remain.

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?

The prose explains how type values compose display text with <name> ('Playing ... <name>') beyond the enum list, which adds some semantic value. However, it does not explain state, details, or application_id, and with 57% schema coverage it only partially compensates.

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?

Names a specific action and resource ('Show an activity on your profile') and enumerates the activity types displayed, making it clearly a presence/activity setter. It does not explicitly differentiate from siblings such as clear_activity or set_headless_activity, so it stops short of 5.

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?

The description implies use for displaying profile activity and states a lifecycle constraint ('Lasts while this MCP is connected'). However, it gives no explicit when-to-use/when-not guidance or alternatives for clearing, headless activity, or status tools, so usage is only implied.

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