Skip to main content
Glama

get_cookies

Read-only

Retrieves cookies for a specified domain to return login credentials, enabling authenticated QQ account operations when there is a clear purpose; do not expose results.

Instructions

获取 Cookies 返回登录凭据,仅在有明确用途时读取,请勿公开。 Returns: { cookies }:指定域名的 Cookie 字符串。

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

Input Schema

NameRequiredDescriptionDefault
domainNoqun.qq.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly=true and destructive=false, but the description adds material context those annotations cannot convey: the result is login credentials, it should only be read with a clear purpose, and it must not be disclosed publicly. It also discloses the return shape. It stops short of explaining behavior when no cookies exist for a domain or how long the credentials remain valid.

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 sentences: the sensitive-data warning is front-loaded and the return contract is appended. Nothing is padded, though the mixed-language phrasing makes the read slightly less clean than a single-language statement would.

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 one-parameter read-only tool with annotations covering safety and no output schema, the description supplies the essential missing pieces: credential sensitivity, a disclosure warning, and the return key. The remaining gap is the undocumented default-domain behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the schema alone leaves the single `domain` parameter (with default qun.qq.com) unexplained. The description partially compensates by tying the parameter to its effect ("指定域名的 Cookie 字符串"), but it never states the accepted domain format or what the default implies when the argument is omitted.

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 gives a specific verb and resource (获取 Cookies / get cookies for a domain) and names the return payload ({ cookies }), so the operation is unambiguous. It does not differentiate itself from closely related siblings such as get_credentials or get_csrf_token, which is the only thing keeping it from a 5.

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 provides a conditional caution ("仅在有明确用途时读取,请勿公开"), which implies usage discipline but is a security warning rather than routing guidance. It never says when to prefer this over get_credentials or get_csrf_token, so the agent must infer the choice from names alone.

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