Skip to main content
Glama

get_login_info

Read-only

Retrieve the current logged-in QQ account number and nickname to identify which account is active before reading or sending messages.

Instructions

get_login_info Returns: 当前登录账号的 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_login_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/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 and the description needn't repeat it. The description usefully discloses the return payload (QQ number and nickname), which matters because no output schema exists, but it says nothing about failure behavior when no account is 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.

Conciseness4/5

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

It is a single short sentence with no padding. The only waste is the redundant restatement of the tool name ('get_login_info Returns:'), and the substantive content — what is returned — is front-loaded.

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 zero-parameter read tool, the essential information is what comes back, and that is stated. However, with no output schema and three closely related login tools in the sibling set, the description should say how this differs from qq_login_status and what happens when unauthenticated; it leaves both unaddressed.

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 there is no parameter semantics to explain and the baseline of 4 applies. The schema is a bare object with additionalProperties=true, and nothing in the description conflicts with that.

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 the outcome concretely: it returns the QQ number and nickname (QQ 号与昵称) of the currently logged-in account, which is more than a restatement of the name. It does not, however, distinguish itself from near-siblings such as qq_login_status or qq_login, so the agent must guess which one to call for account identity.

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 mention of prerequisites (must a login already exist?), and no reference to alternatives like qq_login_status. Usage can only be inferred from the tool name and the returned fields.

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