Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_unread

Read-only

Retrieves unread Discord DMs, mentions, and optionally all unread unmuted channels so you can identify messages needing attention.

Instructions

What is unread right now: DMs with new messages, channels where you were mentioned, and (all=true) every unread unmuted channel. Needs the live connection.

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": "list_unread"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoInclude every unread unmuted channel, not just DMs and mentions
guild_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open-world), and the description adds a genuine operational prerequisite not visible in structured fields: it 'needs the live connection.' That is useful context for an agent deciding whether the tool will work in a given session, though nothing is said about what happens if the connection is absent or how results are ordered/limited.

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?

A single front-loaded sentence names the result set first, then the modifier, then the runtime prerequisite. No filler or repetition; every clause carries meaning.

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

Completeness3/5

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

For a two-parameter, read-only list tool with no output schema, the definition covers the main scope question well. It leaves two real gaps: what guild_id does (presumably scoping to one server) and any hint of result shape or volume beyond the category names.

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?

The description restates the meaning of all=true (every unread unmuted channel, not just DMs and mentions), which mirrors but reinforces the schema text. The second parameter, guild_id, is undocumented in the schema's description coverage gap and is not explained at all here, so the 50% coverage is not fully compensated.

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?

States a concrete verb-like scope (what is unread right now) and enumerates the three resources returned: DMs with new messages, mention channels, and with all=true every unread unmuted channel. That cleanly separates it from plain listing tools like list_dms, though it does not name any sibling explicitly.

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 implied by the 'unread right now' framing, which tells an agent to reach for this when it wants pending items rather than full channel/DM lists. However, no when-not guidance or explicit alternative is given, and the effect of the guild_id scoping is left entirely implicit.

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