Skip to main content
Glama

fetch_custom_face_detail

Read-only

Retrieve custom QQ emoticon details, including resource IDs, image URLs, summaries, and descriptions, to display or manage account faces.

Instructions

获取自定义表情详情 Returns: 自定义表情详情数组,包含资源标识、图片地址、摘要与描述。

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

Input Schema

NameRequiredDescriptionDefault
countNo

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 safety is covered. The description adds value by disclosing the return shape (an array of details with resource identifier, image URL, summary, description), which matters because no output schema exists. It still says nothing about volume, paging, or how the 'count' interacts with the returned array.

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, front-loaded with the action and then the return summary, with no filler. The split between a Chinese action phrase and a Chinese return clause is compact and readable.

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 single-parameter read tool, the description covers the return payload, which is the biggest gap given there is no output schema. However, the unexplained 'count' parameter and the unresolved overlap with fetch_custom_face/fetch_face_entity keep it from being complete.

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?

Only one parameter ('count', default 48, minimum 0) exists and schema description coverage is 0%, so the description carries the explanatory burden. It never mentions 'count' at all and never explains whether it bounds the returned array size; the only semantic value it adds is about outputs, not inputs.

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 ("获取自定义表情详情" – fetch custom face detail) and even summarizes the returned payload, so the operation is clear. It does not distinguish itself from sibling tools such as fetch_custom_face or fetch_face_entity, leaving ambiguity about when this 'detail' variant is the right call.

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 when-to-use guidance, no prerequisites, and no mention of the sibling alternatives (fetch_custom_face, fetch_face_entity) that an agent must choose between. Usage is only implied by the word 'detail'.

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