Skip to main content
Glama

fetch_face_entity

Read-only

Retrieves QQ system emoji details by numeric or string ID, returning null when the ID does not exist and optionally refreshing the QQ catalog.

Instructions

按编号查询 QQ 系统表情 Returns: 表情详情;编号不存在时返回 null。

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

Input Schema

NameRequiredDescriptionDefault
face_idYesQQ 系统表情编号
refreshNo是否强制从 QQ 刷新目录

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds a genuinely useful behavioral fact: it returns null when the face ID does not exist. It does not say what happens when refresh=true, whether the refresh has cost (network/cache), or what fields the 'face details' contain.

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, front-loaded with the lookup purpose, and the return behavior attached immediately. No wasted wording; the only blemish is the inline 'Returns:' mixed into the sentence rather than structured separately.

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 simple read-only lookup with full schema coverage and no output schema, the definition covers the essentials: what it looks up and the null-on-missing outcome. The only real gap is not explaining the effect of refresh=true, which the schema touches on only briefly.

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%, so the schema already defines both face_id and refresh, including the default for refresh. The description only restates that lookup is 'by ID'; it adds nothing about accepted ID formats (integer vs string is in the schema but not explained) or what refresh implies in practice. 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: look up a QQ system emoji by its ID ('按编号查询 QQ 系统表情'). The modifier '系统表情' (system face) implicitly distinguishes it from the custom-face siblings, but no sibling is named explicitly and no other tool is named as the alternative.

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?

There is no explicit when-to-use or when-not-to-use guidance. The word '系统表情' vs. the sibling names like fetch_custom_face imply the distinction, but that inference is not stated. It never says to use fetch_custom_face for custom faces instead.

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