Skip to main content
Glama
Sign In
better-discord-mcp

better-discord-mcp

by Sys0xdbg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

discord_thread_add_member

Add a user to a Discord thread by providing their user ID and thread ID.

Instructions

Add a member to 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>",
      "userId": "<userId>"
    },
    "name": "discord_thread_add_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYes
threadIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are given, and the description fails to disclose behavioral details like required permissions, thread type restrictions, or side effects on the user's state.

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?

The description is extremely concise (6 words) and front-loaded, but it omits essential details that are needed for correct use.

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?

With no output schema, no annotations, and two opaque parameters, the description is incomplete. A mutation tool needs more context about effects and prerequisites.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not explain the two required parameters (threadId, userId), and the input schema has 0% coverage. An agent cannot infer what values to provide.

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

Purpose5/5

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

The description clearly states the action: 'Add a member to a thread.' It uses a specific verb and resource, and distinguishes from sibling tools like discord_thread_remove_member and discord_thread_join.

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?

No guidance is provided on when to use this tool versus alternatives, such as requiring permissions, membership prerequisites, or threading contexts.

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