Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_notification_settings_snapshots

Read-only

Lists snapshots of the current user's Discord notification settings, enabling review of saved configuration states.

Instructions

List Notification Settings Snapshots. [GET /users/@me/notification-settings/snapshots]

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

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?

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered by structured data. The description adds nothing beyond those annotations — no mention of pagination, result ordering, snapshot retention, or what a snapshot even represents in this API.

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 short, front-loaded fragments with no filler. Nothing is wasted, though the second fragment is a bare URL rather than an English clarification of scope.

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?

This is a simple parameterless read, but there is no output schema and the description never indicates what a 'snapshot' object contains or how many are returned. Given the ambiguity of the domain term, the definition leaves the agent guessing about the response shape.

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 nothing for the description to disambiguate; the baseline for a parameterless tool applies. The endpoint path is a minor extra that confirms it is a self-scoped read.

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 states a specific verb ('List') and resource ('Notification Settings Snapshots'), and the appended endpoint path '[GET /users/@me/notification-settings/snapshots]' usefully pins the scope to the current user's own snapshots. It does not, however, distinguish this from sibling tools such as create_notification_settings_snapshot or delete_notification_settings_snapshot beyond the verb.

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 versus the create/delete snapshot siblings or the notification-center listing tools. The agent must infer usage purely from the name and HTTP path, and no prerequisites or exclusions are given.

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