Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_list_blocked

Lists users blocked by the signed-in Discord account so you can review or manage the block list.

Instructions

List blocked users.

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_list_blocked"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, but it discloses almost nothing: it doesn't say whether this is a safe read operation, whether the blocks are user-account rather than bot-account scoped, whether authentication for a user token is required, or whether results are paginated. The only information conveyed is the resource being listed.

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 one short, front-loaded sentence with no wasted words. Brevity is fine here, but the single sentence leaves too much unsaid rather than being optimally economical.

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 annotations and no output schema, the description is the only source of behavioral context, yet it says nothing about the return shape, pagination, or authentication. For a simple zero-parameter lister that is tolerable, but it is not sufficient to invoke with confidence.

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 no parameter meaning for the description to add. The baseline for a parameterless tool 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 uses a specific verb plus resource ("List blocked users"), which is enough to tell it apart from most siblings such as discord_list_members or discord_list_channels. It stops short of clarifying how this differs from discord_list_bans, which is the nearest neighbor an agent could confuse it with.

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 guidance on when to use this tool rather than discord_list_bans, discord_list_friends, or discord_list_friend_requests, even though the description's job here is to disambiguate similar list tools. No preconditions or exclusions are stated.

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