Skip to main content
Glama

get_rkey_server

Read-only

Retrieves QQ rkey server details such as expiry time and available private or group rkeys needed for authenticated messaging; handle returned credentials as sensitive data.

Instructions

获取 rkey 服务器信息 返回值可能包含凭据或临时下载密钥,请勿公开或记录到不受控日志。 Returns: { expired_time, name, private_rkey?, group_rkey? }:rkey 过期时间与(存在时的)私聊/群聊 rkey。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds important context beyond that: the result may contain credentials or temporary download keys and must not be publicly exposed or logged to uncontrolled logs.

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?

The description is compact and front-loads the purpose, then adds the security warning and return-shape details. Every sentence contributes useful information, though the bilingual formatting is slightly less clean than a single-language description.

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 parameters and no output schema, the description supplies the key return fields and a critical security caveat. It is nearly complete for a simple read tool, though it could mention authentication or environment expectations for an open-world rkey server lookup.

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 has zero parameters, so there are no parameter semantics to explain. The description correctly focuses on behavior and return values instead of inventing parameter guidance.

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 states a specific verb and resource: fetching rkey server information. It also names the returned fields, making the resource clear, but it does not explicitly differentiate this tool from nearby siblings such as get_rkey or get_credentials.

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?

The description does not state when to use this tool instead of alternatives, nor does it give prerequisites or exclusions. Usage is only implied by the tool name and return fields, and the security warning is about handling results rather than when to invoke the tool.

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