Skip to main content
Glama

fetch_super_face_id

Read-only

Checks whether a QQ system face ID uses the super emoji format, optionally refreshing the face directory.

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": {
      "face_id": "<face_id>"
    },
    "name": "fetch_super_face_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
face_idYesQQ 系统表情编号
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, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that the result is a boolean 'whether it uses super format', which is useful given there is no output schema, but it says nothing about the network fetch implied by openWorldHint or the refresh parameter.

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 sentences with the purpose front-loaded. The 'Returns:' clause partly repeats the purpose statement, which is mild redundancy rather than waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter boolean check, the description covers purpose and return type, but it never explains what 'super face format' means in practice or what the agent should do differently for a true result. It does not mention caching or when setting refresh would matter.

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%: face_id is documented as the QQ system face number and refresh as forcing a refresh from the QQ directory. The description adds no further meaning about either parameter, so the baseline score of 3 is appropriate.

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: judging whether a QQ system emoji (face_id) uses the 'super face' format, i.e. a boolean predicate. It is not a tautology of the name, but it offers no explicit differentiation from related sibling tools such as fetch_sys_faces or fetch_face_entity.

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 statement about when to call this tool versus alternatives, and no prerequisites or exclusions are given. The only hint of usage is implied by the predicate semantics: check format before constructing or sending a face.

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