Skip to main content
Glama

request_decrypt_key

Requests the decryption key for a SnowLuma database path tied to the current QQ account; use it to retrieve the sensitive key needed to decrypt that database.

Instructions

请求数据库解密密钥 路径位于 SnowLuma 服务端,必须指向当前账号可用的数据库;返回值是敏感密钥。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "db_path": "<db_path>"
    },
    "name": "request_decrypt_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
db_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true, destructiveHint=false; the description adds genuinely new context: the path is server-side (not a local/agent path), it is scoped to the current account's databases, and the return value is a sensitive secret. That last point is important operational information an agent would not get from the annotations. It still doesn't say whether the key is cached, logged, or rate-limited.

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 compact clauses, front-loaded with the action and resource, then the path constraint, then the return-value warning. No filler; slightly denser than ideal because the constraint and the sensitivity note are packed into one sentence.

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 single-parameter tool with annotations covering the safety profile and no output schema, the definition covers what to pass, where the path resolves, and that the result is sensitive. Missing only edge-case behavior (invalid path, permission denial), which is minor at this complexity.

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?

Schema coverage is 0% — db_path is documented only as a non-empty string — so the description carries the full burden, and it does add real semantics: the value is a server-side path, not a client path, and it must resolve to a database the current account can use. It stops short of giving an example format or expected prefix.

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 a specific verb and resource ('请求数据库解密密钥' – request the database decryption key), so an agent knows exactly what the tool produces. It does not differentiate from any sibling, but the sibling list contains no comparable key/secret tool, so the risk of misselection is low.

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?

It gives one real prerequisite: db_path must be on the SnowLuma server and must reference a database available to the current account. It offers no when-to-use vs. when-not guidance, no alternatives, and no statement about failure modes when the path is invalid or inaccessible.

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