Skip to main content
Glama

nc_get_user_status

Read-only

Retrieves a QQ user's online and extended status codes by user ID, helping you check availability or presence before interacting.

Instructions

获取用户在线/扩展状态 替换为需要查询的 QQ 号。 Returns: { status, ext_status }:用户在线状态码与扩展状态码。

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

Input Schema

NameRequiredDescriptionDefault
user_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered by structured data. The description adds a return shape ({status, ext_status}) that no output schema provides, which is meaningful extra context, though it says nothing about failures or missing users.

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 description is short and front-loads the purpose, but a leftover placeholder sentence sits between the purpose and the return-value note, adding noise an agent must parse past. The structure would be better if the purpose and return information were adjacent.

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 one-parameter read tool with annotations covering safety, the description supplies both purpose and return fields, which is close to adequate. It still lacks any usage routing among the many sibling status/setter tools, which is the main gap for an agent choosing between them.

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%, so the schema alone does not explain user_id. The description partially compensates by indicating that the single parameter is the QQ number to look up, but this appears as a garbled template instruction ('替换为需要查询的 QQ 号') rather than a clean parameter definition, and the accepted integer/string forms are not 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 names a specific verb and resource: it gets a user's online status plus extended status, which lets an agent distinguish it from the set_online_status and set_input_status siblings. The purpose is clear, though the embedded template line about replacing a QQ number slightly muddies the opening.

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?

The description gives no guidance on when to use this tool instead of related tools. Siblings such as get_status, qq_login_status, and get_user_status-style alternatives exist, yet the description never states which condition should lead an agent here.

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