Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

clear_activity

Removes the current Discord activity set with set_activity while preserving your custom status.

Instructions

Remove the activity set with set_activity (keeps your custom status).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 declare readOnlyHint=false with destructiveHint=false, so the agent knows this mutates state without being destructive. The description adds genuine behavioral context beyond that: the custom status is preserved, which is exactly the sort of side-effect an agent needs. It does not disclose idempotency or auth requirements.

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?

One short sentence with the action front-loaded and the preserved-status caveat parenthesized at the end. Slightly awkward phrasing ('with set_activity' could be read as an argument rather than a tool reference), but nothing 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 zero-parameter, no-output-schema mutation the description covers the essentials: what is removed, what survives, and which tool it reverses. It omits error/no-op behavior and confirmation of the resulting state, which keeps it at adequate rather than complete.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The parenthetical about custom status is the only semantic detail available and is well placed.

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 uses a specific verb ('Remove') on a specific resource ('the activity set') and names the sibling tool set_activity as the counterpart that created it, so the agent can tell it is the inverse operation. It stops short of stating the effect in full sentences, but the purpose is unmistakable.

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 reference to set_activity implies the use case: call this when an activity previously set through that tool should be undone. There is no explicit when-not guidance, no statement about what happens when no activity is set, and no other alternative named.

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