Skip to main content
Glama

whoami

Read-only

Retrieves the logged-in QQ account's number, nickname, online status, and friend/group counts so you can verify the session before sending messages or managing groups.

Instructions

Who is logged in: QQ number, nickname, online status, and how many friends/groups. Start here.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 value the annotations cannot: it enumerates the concrete data returned (QQ number, nickname, online status, friend/group counts), which is important given there is no output schema. It does not mention session/auth requirements, but those are implied by 'logged in'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short clauses: the returned fields are front-loaded and the directive 'Start here' closes it. No sentence is wasted and there is no redundant restatement of the name.

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 zero-param, read-only, no-output-schema tool, the description covers exactly the thing an agent cannot get elsewhere: the shape of the result. It omits any mention of failure behavior when no session exists, a minor gap for a tool whose annotations already establish it as a safe read.

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 and there is no parameter semantics for the description to compensate for. The description correctly implies the call is param-free by framing it as an identity lookup with no filtering options.

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 plainly states what the tool yields: account identity (QQ number, nickname), online status, and friend/group counts. It is distinguishable from all siblings, which are actions on messages, files, and groups, but it never uses an explicit verb+resource form and does not route to any alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

'Start here' implies this is an orientation/discovery call to make before other operations, which is genuine, if terse, context. There is no explicit when-not condition, no prerequisite statement, and no named alternative, so usage guidance remains inferred rather than stated.

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