Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

mark_read

Marks a Discord channel or DM, an entire server, or all messages as read; specify channel_id, guild_id, or all=true.

Instructions

Mark as read: one channel/DM (channel_id), a whole server (guild_id), or everything (all=true).

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

Input Schema

NameRequiredDescriptionDefault
allNo
guild_idNo
channel_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), so the bar is lower. The description adds useful scope semantics — that the operation can be narrowed to one channel, one guild, or applied globally — which is context the annotations do not provide, though it says nothing about reversibility or effect on unread counts.

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 sentence, front-loaded with the action, then a clean enumeration of the three scoping options. No filler and no redundancy.

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

Completeness4/5

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

For a three-parameter, no-output-schema write tool this covers what an agent needs to invoke it correctly. The remaining gap is precedence/exclusivity between the three optional parameters, which matters because none of them are required.

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?

Schema description coverage is 0%, so the description must carry all parameter meaning, and it does: it explicitly ties channel_id to 'one channel/DM', guild_id to 'a whole server', and all=true to 'everything'. It falls short of a 5 because it never says whether these are mutually exclusive or which wins if several are supplied.

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 gives a specific verb ('mark as read') plus the three resources it can apply to, so an agent immediately knows what the tool does. It does not name a sibling such as bulk_update_read_states or delete_read_state to differentiate itself, which keeps it short of a 5.

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 entirely through parameter choice: pass channel_id for one channel/DM, guild_id for a server, all=true for everything. There is no statement of who should use it, no exclusions, and no pointer to the related bulk/delete read-state siblings.

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