Skip to main content
Glama

set_online_status

Set or change the current QQ account's online status by specifying the desired status code, with optional extension and battery details.

Instructions

设置在线状态 修改当前账号状态;具体状态码须与目标状态对应。

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": {
      "status": "<status>"
    },
    "name": "set_online_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYes
ext_statusNo
battery_statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare a non-read-only, non-destructive, open-world write, so the description need not restate that. It adds only the scoping fact that the current account is affected, and says nothing about which status codes exist, what ext_status or battery_status do, or whether other clients see the change.

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 short clauses with the action front-loaded and no filler. It is efficient, though its brevity comes at the cost of the detail flagged elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter mutation with no output schema and zero schema description coverage, the definition should explain the status code domain and the two auxiliary integer fields. As written, an agent knows it is setting presence but not what values are valid or what the side effects are.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameter burden, yet it only alludes to a 'status code' mapping without listing any codes or explaining the 'not const 0' constraint. ext_status and battery_status are never mentioned at all, leaving two of three parameters undocumented anywhere.

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 clear verb and resource ('设置在线状态 修改当前账号状态'), making it obvious this mutates the logged-in account's presence state. It does not, however, distinguish itself from the closely related sibling set_diy_online_status, leaving the agent to guess which one applies.

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 prerequisites, and no mention of alternatives such as set_diy_online_status or the get_status family. The only hint is that the status code must match the intended state, which is too vague to route an agent.

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