Skip to main content
Glama

get_friend_dress

Read-only

Retrieve active QQ profile decorations—including pendants, cards, call effects, and input status—for a specified QQ number, returning an empty items array when none are in use.

Instructions

获取指定 QQ 号正在使用的个性装扮(挂件/名片/来电/输入状态等) 替换为需要查询的 QQ 号。 Returns: 装扮信息;目标未使用任何可查询装扮时 items 为空数组。网络失败、未登录态/风控、页面改版、返回账号与请求不一致时返回失败并附具体原因

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": {
      "user_id": "<user_id>"
    },
    "name": "get_friend_dress"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYes目标 QQ 号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, the description discloses concrete failure modes: network failure, unauthenticated state or risk control, page redesign, and returned account not matching the request, each reported as a failure with a reason. It also states the empty-array success case. It stops short of describing latency, rate limits, or result pagination.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is front-loaded with purpose, then returns, then failure modes, which is a sensible order. However, the sentence fragment '替换为需要查询的 QQ 号' reads like an unfilled template placeholder and adds no information, wasting a line in an otherwise tight description.

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?

With no output schema, the description supplies the return shape (items array, empty when nothing queryable) and the failure semantics, which covers what an agent needs for this one-parameter read tool. Only the leftover placeholder wording slightly undermines an otherwise complete definition.

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 coverage is 100% for the single user_id parameter, so the baseline applies. The description reinforces that the value is a QQ number and hints at validation ('returned account does not match request'), but adds no format or range guidance beyond what the schema already gives.

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 opening states a specific verb and resource: fetch the personalized dress-up items (pendant/card/call/input status, etc.) currently in use by a given QQ number. The 'currently in use' scope distinguishes it from a hypothetical historical or catalog lookup, but no sibling tool is named, so there is no explicit contrast with the rest of the catalog.

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?

Usage is implied by the purpose statement and the empty-array case clarifies what a 'no results' outcome means. However, there is no explicit when-to-use/when-not-to-use guidance and no named alternative for related queries, leaving routing decisions to inference.

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