Skip to main content
Glama

qzone_user_card

Read-only

Retrieve a QQ user's Qzone profile card by QQ number, including nickname, avatar, Qzone name, and whether the space can be visited.

Instructions

Someone's 空间 name card (nickname, avatar, 空间 name, whether you can visit, etc.).

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": {
      "uin": "<uin>"
    },
    "name": "qzone_user_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
uinYesQQ number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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 field-level content about what the card contains, including the privacy-relevant 'whether you can visit' flag, which is genuinely useful context, but it says nothing about auth requirements or visibility failures when access is denied.

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?

One compact sentence with no filler; the resource and its contents are front-loaded. The trailing 'etc.' weakens precision slightly by leaving the return set open-ended.

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 one-parameter read-only tool with full schema coverage and annotations, the description covers what it fetches and roughly what comes back. The main omissions are differentiation from get_qzone_profile and any note on access-restricted results.

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 uin parameter is already documented as 'QQ number'. The phrase 'Someone's' subtly implies the target can be any user rather than the caller, which is a small addition, but the description never names uin or explains accepted integer/string forms.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource as a user's Qzone (空间) name card and enumerates some returned fields (nickname, avatar, 空间 name, visit permission). However, it is a noun fragment with no explicit verb, and it does not differentiate itself from the nearby get_qzone_profile sibling, which an agent could easily confuse it with.

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 mention of prerequisites (login/cookies), and no statement of whether this works for the caller's own uin or only for other users. The agent must infer the usage context entirely.

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