Skip to main content
Glama

fetch_sys_faces

Read-only

Retrieves the full QQ system emoji catalog grouped by category, with an optional refresh to force the mapping from QQ.

Instructions

获取 QQ 系统表情目录 Returns: 按分组返回完整的 QQ 系统表情映射。

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

Input Schema

NameRequiredDescriptionDefault
refreshNo是否强制从 QQ 刷新目录

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/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 that results are returned grouped by category, which helps the agent anticipate the shape, but it says nothing about caching, freshness, or rate limits beyond what the schema's refresh flag already conveys.

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 sentences, with the resource named first and the return shape second. There is no filler, though the 'Returns:' prefix is slightly redundant given the preceding sentence.

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?

For a one-parameter, read-only catalog tool with no output schema, the definition is adequate: it names the resource, notes grouped return structure, and annotations cover safety. The main remaining gap is the absence of any routing guidance relative to sibling lookup tools.

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 coverage is 100% and the single refresh parameter is fully documented in the schema ('是否强制从 QQ 刷新目录'). The description adds no meaning beyond that schema text, so the baseline 3 applies.

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 and resource: fetching the complete QQ system emoji catalog. The word '完整' (complete) implicitly distinguishes it from search_sys_faces, though it never names that sibling explicitly.

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 explicit when-to-use guidance, no mention of when to prefer search_sys_faces over this bulk catalog fetch, and no stated prerequisites. The agent must infer the choice from the word 'complete' 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