Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_notification_center_items

Read-only

Retrieves items from your Discord notification center inbox, such as friend requests and reminders, with filters for mentions, roles, and everyone pings, plus pagination by item ID and result limits.

Instructions

Notification center (activity inbox: friend requests, reminders…). [GET /users/@me/notification-center/items]

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

Input Schema

NameRequiredDescriptionDefault
afterNoReturn items after this ID (pagination)
limitNoMax results
roles_filterNoroles filter
with_mentionsNowith mentions
everyone_filterNoeveryone filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds only a raw REST path, disclosing nothing about ordering, pagination behavior, default limits, or what kinds of items appear in the inbox.

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?

Two compact fragments with no filler, and the resource gloss comes first. The bracketed HTTP endpoint notation is developer-facing noise that does little for an agent, but it costs little space.

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?

Five optional parameters and no output schema means the description should explain what a listing returns and how the cursor/limit combine; it explains neither. Filter semantics (roles_filter vs everyone_filter vs with_mentions) are left entirely ambiguous, which is a real gap for an agent composing a query.

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 the baseline is 3, and the description adds nothing on after/limit/roles_filter/with_mentions/everyone_filter. Notably the schema's own descriptions ('roles filter', 'everyone filter') are tautological, so the description had a chance to compensate on the filter semantics and did not.

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 parenthetical 'activity inbox: friend requests, reminders…' gives concrete examples that identify the resource, but there is no verb and no scope statement. It is enough to guess this returns inbox entries, but hardly a specific verb+resource claim that separates it from siblings like list_friends or list_friend_suggestions.

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?

The description says nothing about when to call this instead of acknowledge_notification_center_item, bulk_acknowledge_notification_center_items, or delete_notification_center_item, nor any prerequisite or ordering guidance. The agent must infer usage from the name alone.

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