Skip to main content
Glama

get_csrf_token

Read-only

Fetch the CSRF token needed to authenticate QQ account actions and include it in subsequent requests.

Instructions

获取 CSRF 令牌 Returns: { token }:CSRF 令牌(bkn,数值)。

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

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?

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered by structured data. The description adds value beyond that by disclosing the return payload shape '{ token }' and its nature ('bkn,数值' — a numeric bkn value), which is the most important behavioral detail for a token-fetch tool with no output schema. It stops short of noting token lifetime or session binding.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short clauses: purpose first, then the return shape. Nothing is padded or redundant, and the most decision-relevant information is front-loaded.

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?

Because there is no output schema, the description correctly takes on the burden of describing the return value, and it does so adequately. However, for a token tool the missing context — why the token is needed, whether it expires, and how it relates to the credential/clientkey siblings — leaves the definition only minimally complete.

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 and there is no parameter semantics for the description to compensate for. The schema is an open object, consistent with a no-argument call.

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?

States a specific verb and resource ('获取 CSRF 令牌' / get CSRF token), which is unambiguous about what the tool returns. It does not differentiate from nearby credential-fetching siblings such as get_clientkey, get_credentials, or get_cookies, so an agent cannot tell from the text alone which one it needs.

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 versus alternatives, no statement that the token is a prerequisite for other authenticated calls, and no note about whether it must be fetched per-session or refreshed. The agent is left to infer the entire usage context.

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