Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

start_typing

Displays the "is typing…" indicator in a Discord channel for about 10 seconds to signal an incoming reply or activity.

Instructions

Show "is typing…" in a channel for ~10 seconds. [POST /channels/{channel_id}/typing]

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

Input Schema

NameRequiredDescriptionDefault
channel_idYesChannel ID (text, voice, thread, forum or DM channel)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the write-but-not-destructive profile is covered. The description usefully adds the ~10 second lifetime, which is behavior the agent could not get from the annotations or schema. However, it says nothing about rate limiting, which is the main operational hazard for a typing endpoint that must be refreshed.

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?

One front-loaded sentence stating the effect and duration, followed by the endpoint reference. Nothing is redundant and the actionable detail comes first.

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 one-parameter, no-output-schema, non-destructive write tool, this is nearly sufficient: purpose, expiration, and endpoint are all stated. The only meaningful omission is refresh/rate-limit guidance, which matters because the indicator lapses after ~10 seconds.

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% and the single channel_id parameter is documented there as accepting text, voice, thread, forum, or DM channels. The description only echoes the path template, adding no semantics beyond the schema, so the baseline of 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?

The description gives a precise verb and effect ("Show 'is typing…' in a channel") plus the underlying endpoint POST /channels/{channel_id}/typing, so the agent knows exactly what the call does. It does not name any sibling or contrast case, but the action is distinctive enough that confusion is unlikely.

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?

Usage is only implied: the agent can infer it should call this to simulate a typing indicator, but the description never says when to use it versus sending a message, nor whether it must be re-called to sustain the indicator. No exclusions or alternatives are offered.

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