Skip to main content
Glama

get_rkey

Read-only

Retrieves a temporary download key for accessing QQ downloads, returning credentials that must not be exposed or logged in uncontrolled systems.

Instructions

获取下载 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"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 description's real contribution is the disclosure that the return value may contain credentials or temporary download keys and must not be publicly exposed or written to uncontrolled logs. That is genuinely useful behavioral context an agent would not otherwise have. It stops short of saying whether the key is time-limited, reusable, or tied to the caller's session.

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 short clauses: purpose first, then the security caveat. Nothing is padded. It is arguably too terse for a tool whose purpose rests on an unexplained acronym, but no sentence is wasted.

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 parameters and no output schema, the description carries the burden of explaining what comes back, and it does warn that the payload is sensitive. However, it says nothing about the shape of the result, whether the rkey expires, or how it relates to sibling key-fetching tools, which leaves meaningful gaps for a credential-adjacent operation.

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. The schema leaves additionalProperties open, and the description adds nothing that would matter for invocation since there is nothing to supply.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource ('获取下载 rkey'), which is more than a tautology, but 'rkey' is unexplained jargon and the definition never distinguishes it from close siblings such as get_rkey_server, get_clientkey, or get_credentials. An agent can tell it retrieves something called a download rkey but not why this one is different.

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 guidance on when to call this tool, when not to, or which sibling to prefer for a related need. The only conditional statement is a post-hoc warning about handling the result, not about selecting 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