Skip to main content
Glama

fetch_custom_face

Read-only

Retrieve custom QQ emojis as image URLs or emoji IDs, with an optional count, so AI can include them in messages or workflows.

Instructions

获取自定义表情 Returns: 字符串数组:return_type=url 时为图片 URL,return_type=id 时为 emoji_id。

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

Input Schema

NameRequiredDescriptionDefault
countNo
return_typeNourl

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 genuine behavioral context by explaining what the returned string array contains for each return_type, but is silent on pagination, default count behavior, and whether results are scoped to the current account.

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 clauses: purpose first, then return semantics. No filler, and the return-value note is placed where an agent will look for it, though the abrupt 'Returns:' fragment without punctuation reads slightly run-on.

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?

With no output schema, the description usefully compensates by describing the return array contents, which is the most important missing structured information. It remains incomplete for a two-parameter tool because count is never addressed and there is no hint about result ordering or limits.

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 0% and the schema gives no enum for return_type, so the description's explanation that return_type=url yields image URLs and return_type=id yields emoji_id is real added meaning. However, the count parameter (default 10, minimum 0) is not explained at all, and no accepted values beyond the two named are clarified.

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 ('获取自定义表情' / fetch custom emoji), so the agent knows exactly what is being retrieved. It does not differentiate itself from nearby siblings such as fetch_custom_face_detail or fetch_sys_faces, leaving ambiguity about which fetch tool to pick.

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 of when to use this tool versus the sibling fetch/detail variants, no prerequisites, and no exclusions. The only conditional guidance concerns the return_type values, which is output formatting rather than usage selection.

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