Skip to main content
Glama

get_stranger_info

Read-only

Fetch a QQ user's public profile by QQ number, including account ID, level alias, registration time, birthday, and membership details when available.

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

Input Schema

NameRequiredDescriptionDefault
user_idYesQQ 号

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?

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuinely useful response behavior: which fields may be omitted (registration time, birthday, membership), that only the birth year is dropped when the year is private, and that no placeholder is returned for login days.

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 return-value section is dense and front-loads the important omission rules, but the opening '替换为需要查询的 QQ 号' reads as leftover template/placeholder text rather than guidance, adding noise to an otherwise short definition.

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 carries the burden of explaining the returned profile and its conditional omissions, and it does so thoroughly. Only the absence of guidance on error/not-found behavior or on when to prefer a sibling tool keeps it from a 5.

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% and the single parameter is already documented as 'QQ 号'. The description's '替换为需要查询的 QQ 号' only restates the schema placeholder and adds no format, range, or constraint detail beyond it, so 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 first clause states a specific verb+resource ('获取陌生人信息' – fetch a stranger's profile), which distinguishes it from friend/group-member lookups by scope. It does not name any sibling tool explicitly, so it falls short of a 5.

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 only implied: the agent must infer that this is the tool for a non-friend QQ account when no other info tool applies. There is no explicit when-to-use/when-not-to-use statement and no named alternative such as a friend or group-member lookup.

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