Skip to main content
Glama

get_credentials

Read-only

Retrieves QQ login credentials—cookies, token, and CSRF token—for a specified domain so authenticated account operations can proceed; use only for clear, authorized purposes.

Instructions

获取凭证 返回登录凭据,仅在有明确用途时读取,请勿公开。 Returns: { cookies, token, csrf_token }:Cookie 字符串与 CSRF 令牌(token 与 csrf_token 同值)。

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

Input Schema

NameRequiredDescriptionDefault
domainNoqun.qq.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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, and the description is consistent with a read. Beyond that it adds genuinely useful behavior: the exact return shape { cookies, token, csrf_token }, the fact that token and csrf_token hold the same value, and a sensitivity warning against disclosure — none of which the annotations convey.

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 that front-load the purpose and follow with the return contract and a safety warning. The Chinese and English portions overlap slightly 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 output schema, the description usefully supplies the return field names and the token/csrf_token equivalence. It is still incomplete for a secrets-fetching tool: the domain parameter is unexplained, and there is no indication of what happens when no session exists or how the credentials expire.

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

Parameters2/5

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

The single parameter domain (default qun.qq.com) has 0% schema description coverage and is never mentioned in the description. An agent cannot tell from either source which site or account the credentials belong to, or what changing the default does, so the description fails to compensate for the coverage gap.

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 concrete verb and resource (获取凭证 / returns login credentials) and even enumerates the returned fields, so an agent knows this aggregates cookies plus a CSRF token rather than fetching one specific secret. It stops short of explicitly positioning itself against the siblings get_cookies and get_csrf_token, which return the individual pieces.

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 a cautionary condition — read only when there is a clear purpose, and never expose the result — which implies when to use it. However, it offers no guidance on when to prefer get_cookies or get_csrf_token instead, and no prerequisites or failure conditions are described, so usage is only implied.

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