Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

block_user

Destructive

Blocks a specified Discord user by user ID to prevent unwanted interactions and contact. Use it to stop a user from reaching your account or server.

Instructions

Block a user.

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": {
      "user_id": "<user_id>"
    },
    "name": "block_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is partly covered. The description adds nothing beyond 'Block a user' — it does not explain the effects of blocking, whether it is reversible, what permissions are required, or what side effects occur.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is only one short sentence and is front-loaded, but it is under-specified rather than usefully concise. It wastes no words, yet it also does not earn its place by conveying enough information for a destructive operation.

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?

This is a destructive user-affecting operation with one undocumented parameter and no output schema. Given the complexity and the annotation hints about destructiveness, the description should explain effects, reversibility, and required inputs; it omits all of these.

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

Parameters2/5

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

The schema has one required parameter, user_id, with 0% description coverage. The description does not mention the parameter at all, so it fails to compensate for the missing schema semantics; the property name is self-explanatory, which prevents a lower score.

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?

The description states a specific verb and resource ('Block a user'), so the basic action is identifiable. However, it does not clarify what blocking entails or distinguish this from adjacent moderation tools such as 'ignore_user', leaving the purpose minimally viable rather than fully clear.

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, and no mention of alternatives or exclusions. The agent only knows that this performs a block, not when to choose it over related user-moderation or ignore operations.

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