Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_clear_status

Resets Discord activity and presence to online, removing any active status or custom activity.

Instructions

Clear activity and presence back to online.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It honestly discloses the resulting state (presence resets to online), which is the most important behavioral fact about the tool. However, it does not say whether the reset applies only to the current session or across clients and devices, whether the call is reversible or harmful, or whether the caller's own account state is modified. For a mutation with no annotation coverage, that is a real gap.

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 ten-word sentence states the action first, then the resulting state. There is no filler, and the key fact is front-loaded. Nothing could be removed without losing information.

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?

The tool is trivially simple (zero parameters, no output schema, no annotations), so the description is close to adequate in size. But because no annotations declare behavior, the description should have said more about the scope of the reset (for example, whether it affects all connected clients and what state the account is left in). It is enough to call the tool, but not enough to predict its full effect.

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 is 4. The description correctly supplies no parameter detail, matching the empty schema. A 5 is not warranted because there is no semantic depth to add here.

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 pairs a specific verb, "Clear," with a specific resource, "activity and presence," producing a purpose an agent can state without opening a schema. It also names the resulting state ("back to online"), which pins down the effect. It falls short of a 5 because it never distinguishes this tool from its obvious siblings, discord_set_custom_status and discord_set_status.

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?

The description gives no explicit guidance on when to choose this over discord_set_status or discord_set_custom_status, no prerequisites, and no exclusions. Only the barest implied usage is present: to remove a status, call this. An agent must infer the routing from the verb "Clear" alone.

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