Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

set_headless_activity

Displays a playing activity without a gateway connection and returns a token for later deletion. Use it to set headless Discord presence sessions.

Instructions

Show a "playing" activity without the gateway (headless session). Returns a token to delete it later. [POST /users/@me/headless-sessions]

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

Input Schema

NameRequiredDescriptionDefault
tokenNotoken
activitiesYes[{name, type: 0, application_id?, state?, details?}]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

The description adds real behavior beyond the annotations: it discloses that the call creates a persistent session and returns a token required for later deletion, which the readOnlyHint/destructiveHint/openWorldHint flags do not convey. It does not state session lifetime or permissions, but the lifecycle hint is the key fact an agent needs.

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?

Two short sentences, purpose front-loaded, then the return-value caveat, then the endpoint annotation. No filler; the bracketed route is the only mildly redundant element.

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 two-parameter mutation with no output schema, the description covers what it does, that it returns a token, and that the token is needed for cleanup. Remaining gaps (session duration, which sibling to use under a live gateway) are secondary.

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 description coverage is 100%, so the properties are already documented. The description adds nothing about the accepted shape of `activities` (name, type, state, details) or how `token` is to be used beyond the schema's own text, so baseline 3 applies.

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?

"Show a 'playing' activity without the gateway (headless session)" gives a specific verb (show/set) plus a specific resource (playing activity) and a distinguishing mode (headless, no gateway). It is clearly not the same as a gateway-backed status set, though it never names the sibling it replaces.

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 parenthetical "without the gateway (headless session)" implies the selection condition — use this when you have no gateway connection — but no explicit when/when-not rule or named alternative (e.g. set_activity, clear_activity) is given. Usage is implied rather than 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