Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_sticker_packs

Read-only

Retrieve available Discord sticker packs and their details so you can browse sticker sets or find pack IDs for message and server customization.

Instructions

List Sticker Packs. [GET /sticker-packs]

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety and remote-call profile is covered structurally. Beyond restating the resource and appending the HTTP route, the description adds nothing — not whether the full global catalog is returned, whether the result is paginated or cacheable, or how large the response is.

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 terse fragments, front-loaded with the operation and with no filler. The bracketed endpoint is mildly redundant with the tool's purpose but does convey the underlying route, so it earns a small amount of its 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?

For a no-parameter, no-output-schema list tool the bar is low, but the openWorldHint tells the agent this hits a remote API and the description never says whether results are complete or paginated, or roughly how much data comes back. That leaves the agent unable to plan follow-up calls from the definition alone.

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 no parameter semantics for the description to compensate for; the baseline of 4 applies. No misleading or missing parameter information exists.

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 names a specific verb and resource ("List Sticker Packs"), which is unambiguous and distinguishable from the singular sibling get_sticker_pack. It does not explicitly call out that distinction, but the singular/plural naming plus the endpoint hint makes the scope clear.

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 only implied: an agent can infer this is the tool for enumerating all sticker packs, but there is no explicit when-to-use guidance and no mention of get_sticker_pack as the alternative when a single pack is needed. Adequate for a zero-parameter list call, but nothing is stated outright.

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