Skip to main content
Glama

search_sys_faces

Read-only

Find QQ system emojis by number, name, alias, or group name and get a matching list.

Instructions

搜索 QQ 系统表情 Returns: 匹配编号、名称、别名或分组名的表情列表。

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": {
      "query": "<query>"
    },
    "name": "search_sys_faces"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes编号、名称、别名或分组名

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, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the return shape (a list of faces matching id, name, alias, or group), which is useful, but says nothing about ordering, limits, or what happens with no matches.

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 clauses, purpose first and return value second, with no filler. The only minor flaw is that the 'Returns:' label is appended inline rather than separated, but nothing is wasted.

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 search with full schema coverage, the definition is nearly sufficient: it names the resource and describes the result set. It would be complete with a note on matching semantics or empty results, but no output schema exists so the return sentence carries that load reasonably well.

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%, and the single query parameter is documented in the schema. The description restates the same accepted value kinds (编号、名称、别名或分组名) without adding format details such as exact-match versus substring behavior, so it stays at the baseline.

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 gives a specific verb and resource ('搜索 QQ 系统表情'), so the agent immediately knows it queries the built-in QQ face catalog rather than chat messages. It does not, however, distinguish itself from the sibling fetch_sys_faces, leaving the boundary between the two implicit.

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 pick this tool over fetch_sys_faces, which is a plausible alternative for retrieving faces. The only contextual hint is the stated return value, which implies usage rather than declaring it.

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