Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_join_thread

Join a Discord thread by its thread ID so an agent can participate in that thread's conversation.

Instructions

Join a thread.

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

Input Schema

NameRequiredDescriptionDefault
threadIdYesDiscord id (snowflake)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the entire behavioral burden and discloses nothing: not whether the operation is idempotent, whether it requires channel access or specific permissions, what changes on the server, or whether joining notifies anyone. "Join a thread" is a restatement of the tool name, not behavioral context, so with zero annotation coverage this is a serious gap.

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?

It is a single short sentence with no wasted words and no burying of the lead. Brevity here is appropriate in form, even though the content is under-specified, which keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation-style tool with no annotations and no output schema, the description should explain access requirements, idempotency, and expected outcome. None of that is present, so an agent cannot call it confidently without external Discord API knowledge.

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?

With exactly one parameter at 100% schema description coverage, the schema already documents threadId as a Discord snowflake with a pattern constraint, so the baseline applies. The description adds no meaning about ID format, sourcing, or failure modes beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Join a thread" states a concrete verb and resource, which is better than a tautology. However, it never clarifies what joining means for this API surface (adding the bot/self to a thread's member list vs. opening a view), and it gives no signal separating it from discord_leave_thread or discord_archive_thread beyond the verb in the name.

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?

There is no when-to-use guidance, no prerequisites (must the caller already have access to the parent channel?), and no mention of any alternative tool. The agent is left to infer everything from the one-line name expansion.

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