Discord MCP

Caixa de entrada

inbox

Read-only

Lists unhandled Discord DMs, mentions, watched channels, and gateway events grouped by conversation, with channel/message IDs ready for reply. Excludes your own messages.

Instructions

Lista o que chegou e ainda nao foi tratado: DMs novas, mencoes a conta, canais vigiados e eventos do gateway, agrupados por conversa e com channelId/messageId prontos para reply_message. Mensagens da propria conta nao contam. Sem cursor, considera as ultimas "hours" horas.

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

Input Schema

Name	Required	Description
`dms`	No	Incluir DMs e grupos. Padrao true.
`hours`	No	Janela, em horas, para canais sem cursor. Padrao INBOX_JANELA_HORAS (48).
`limit`	No	Teto de conversas devolvidas. Padrao 20.
`format`	No	text (padrao) devolve texto compacto; json devolve o objeto bruto.
`watched`	No	Incluir canais vigiados (watch_channel). Padrao true.
`markRead`	No	Marcar tudo o que for devolvido como tratado (avanca cursores e faz ack no Discord). Padrao false.
`mentions`	No	Incluir mencoes a conta em servidores. Padrao true.
`perChannel`	No	Teto de mensagens por conversa. Padrao 8.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 20, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond readOnlyHint/openWorldHint, the description discloses three useful traits: the caller's own messages are excluded, results are grouped per conversation, and IDs are ready to hand to reply_message. The one significant omission is that markRead advances cursors and acks on Discord—a side effect hidden in one schema field on an otherwise readOnly-annotated tool—and the text/json output modes are also unmentioned.

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?

Three dense sentences, front-loaded with scope, then filtering caveat, then window semantics. Nothing repeatable or decorative; every clause carries information.

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?

With eight optional parameters, no output schema, and only two annotation hints, the description does solid work: it defines the item set, the exclusion rule, the grouping, and the window behavior. It falls short on the markRead mutation and the format switch, which materially affect what an agent gets back and what side effects it triggers.

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?

Schema description coverage is 100%, so all eight parameters are already documented, which sets the baseline at 3. The description reinforces the 'hours' fallback window and the implicit dms/mentions/watched filters, but adds no syntax or interaction detail the schema does not already contain.

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?

States a specific verb and resource ('Lista o que chegou e ainda nao foi tratado') and enumerates the four sources it aggregates: DMs, mentions, watched channels, and gateway events. That enumeration plus the 'grouped by conversation' output hint clearly separates it from siblings like read_messages or list_dms, which lack the unhandled-items framing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'still unhandled' scoping tells the agent this is a triage-first tool rather than a raw history reader, and it names reply_message as the natural downstream step. It never explicitly says when to prefer read_messages or mark_read instead, so there is no exclusion guidance, but the usage context is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.