Skip to main content
Glama

get_online_clients

Read-only

Retrieve the current QQ session's online-device snapshot to see which clients are connected. Use the optional no_cache flag to request a refresh, though QQ currently returns only local snapshots.

Instructions

获取在线客户端 Returns: { clients }:QQ 本次会话最近推送的在线设备快照。

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_online_clients"
  }
}

Input Schema

NameRequiredDescriptionDefault
no_cacheNo是否强制刷新;QQ 当前仅暴露本地快照,true 会明确失败

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 the safety profile is covered. The description adds genuinely new behavior: the returned clients are a snapshot most recently pushed by QQ in this session, not a live query, which tells the agent results may be stale — useful context beyond the annotations.

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 two short sentences, front-loaded with the purpose and followed by the return shape. Slight redundancy between "在线客户端" and "在线设备快照", but nothing extraneous.

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 simple read tool with one optional parameter and no output schema, the description supplies both the return key shape ({ clients }) and the freshness caveat, which is enough for an agent to call and interpret it. It lacks only explicit usage/routing guidance.

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?

There is one optional parameter and schema description coverage is 100%, with the schema already explaining no_cache, including the unusual note that true will explicitly fail. The description adds nothing about the parameter, so the baseline 3 for schema-covered parameters 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 description names a specific verb and resource (获取在线客户端) and adds that the payload is a snapshot of online devices, which is concrete and distinguishable from the sibling setters like set_online_status. It does not explicitly contrast itself with any sibling, which keeps it 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The only implicit hint is that the data is "本次会话最近推送的" (last pushed this session), which implies it is a cached snapshot rather than a live query, but the agent must infer that this tool is for reading current online presence.

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