Skip to main content
Glama
Sign In
DSH Sticker MCP

DSH Sticker MCP

by Sylvain-cjh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

qq_list_stickers

List available stickers for the current authorized QQ session and search by tag, note, emotion, or usage to locate the right sticker before visual confirmation and sending.

Instructions

检索当前会话可用的表情库。按标签、备注、情绪和用法查找；标签不能代替视觉确认。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "key": "<key>",
      "token": "<token>"
    },
    "name": "qq_list_stickers"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes当前授权会话 key，由桥接唤醒提示提供
countNo
queryNo
tokenYes当前会话令牌，由桥接提供；不是 OneBot 管理令牌
refreshNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the full behavioral burden. It does disclose one useful caveat: tag matches are not reliable for visual confirmation. However, it says nothing about whether the result is a list, how count/pagination behaves, what refresh invalidates, or what the return shape 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?

The description is two tight clauses that front-load the resource and then name the search dimensions and the caveat. Nothing is padded, though the brevity is partly under-specification rather than pure economy.

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 parameters, no annotations, and no output schema demand more from the description than it delivers. The semantics of count (paging or limiting), refresh (cache behavior), and the shape of the returned sticker entries are all left unstated, so an agent cannot confidently invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 40%: only key and token have inline descriptions. The description never explains query, count, or refresh, even though those are the parameters an agent would most likely get wrong. It mentions finding by tag, note, and emotion but does not map that to the query parameter or explain the 1-100 count limit.

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: retrieve the sticker library available to the current session. That is clearly distinct from the two siblings, which fetch a single image and send a sticker, although the description does not name them explicitly.

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?

The description gives the search dimensions (tag, note, emotion, usage), which implies when to use this tool. The warning that tags cannot substitute for visual confirmation implicitly points to qq_get_sticker_image for verification, but the description never names or explicitly recommends that alternative.

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