Skip to main content
Glama

get_clientkey

Read-only

Retrieves a client key, expiration time, and key index for authenticating QQ account operations; treat returned credentials as sensitive.

Instructions

获取 clientkey 返回值可能包含凭据或临时下载密钥,请勿公开或记录到不受控日志。 Returns: { clientKey, expireTime, keyIndex }:clientkey 及其过期时间与索引。

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

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 partially covered. The description does add real value by warning that the return value may contain credentials or temporary download keys and must not be logged to uncontrolled logs, plus it spells out the returned fields. It does not say whether the key is cached, rotated, or scoped, which would matter for a credential-issuing call.

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 dense sentences with no filler: purpose first, then the security caveat, then the return shape. The front-loading is good, though the return-field list could be separated more cleanly from the warning.

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?

With no output schema, the description usefully enumerates the returned fields (clientKey, expireTime, keyIndex) and flags sensitivity, which covers most of the agent's needs. It omits any statement of prerequisites, scope of the key, or why a caller would choose this over other credential tools, which is a meaningful gap for a credential-issuing tool.

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 and the schema is empty with additionalProperties allowed, so there is nothing for the description to clarify. Baseline 4 applies when there are no parameters.

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 opens with a specific verb+resource (获取 clientkey), so the agent knows it retrieves a client key rather than listing or mutating one. It does not differentiate from nearby credential-like siblings such as get_credentials, get_cookies, or get_csrf_token, leaving the agent to guess which credential source it wants.

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 alternative is named. The agent must infer from sibling names alone that this is one of several credential-fetching tools.

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