Skip to main content
Glama

get_status

Read-only

Retrieve the QQ account's online state, confirmed send/receive link health, and service uptime to verify the account instance is connected and running.

Instructions

get_status Returns: 运行状态。online 表示账号在线;good 表示已确认的收发链路健康状态;time 为当前账号服务实例运行秒数,与 #sl 同源。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description's added value lies in explaining the returned fields. It does define `online`, `good`, and `time`, which matters because there is no output schema. However, it omits what a negative `good` implies and whether the status is scoped to the calling account only.

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?

It is a single compact passage with the return fields front-loaded and each one labeled inline. Minor waste comes from the redundant 'get_status Returns:' prefix and the unexplained '#sl' cross-reference, which adds noise without information.

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 and no parameters, the description carries the return-value burden and does cover all three documented fields. It is nearly complete for a status probe, lacking only interpretation guidance for unhealthy values.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4; there are no inputs to explain. The description correctly focuses on outputs instead of inventing input semantics.

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 phrase 'Returns: 运行状态' only restates the tool name, but the following field-by-field explanation makes the purpose concrete: it returns the current account's online flag, send/receive link health, and service uptime. It is clear what the tool reports, although nothing distinguishes it from siblings such as nc_get_user_status or qq_login_status.

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 guidance on when to call this tool versus nc_get_user_status, qq_login_status, or the set_*_status siblings, and no prerequisites or exclusions are stated. The only contextual cue, '与 #sl 同源' (same source as #sl), refers to an unspecified shorthand and helps neither selection nor invocation.

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