Skip to main content
Glama

qzone_request

Call any QQ Zone web CGI endpoint using your logged-in cookies, with g_tk added automatically and JSON, JSONP, or callback responses parsed.

Instructions

Call any QQ空间 web CGI with your logged-in cookies and g_tk added automatically (escape hatch). url: full https URL, or "host/path" sent via the h5.qzone.qq.com proxy, e.g. "taotao.qq.com/cgi-bin/emotion_cgi_msglist_v6". Parses JSON/JSONP/frameElement.callback responses.

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": {
      "url": "<url>"
    },
    "name": "qzone_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL or host/path
formNox-www-form-urlencoded body
queryNoQuery parameters
methodNoHTTP method (POST when form is given)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Goes meaningfully beyond the annotations by disclosing that login cookies and g_tk are attached automatically, that host/path URLs are routed through the h5.qzone.qq.com proxy, and that JSON, JSONP and frameElement.callback payloads are parsed. It does not warn that arbitrary CGIs may mutate state (annotations only say destructiveHint=false, readOnlyHint=false), nor mention rate limits or error surfacing.

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?

Three dense sentences, front-loaded with the purpose before the escape-hatch caveat and the URL format example. No filler, though the response-format jargon (frameElement.callback) is compact at the cost of readability.

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 four-parameter open-world passthrough with no output schema, it covers the essentials an agent needs: authentication is handled, how URLs are routed, and how responses are decoded. It leaves the agent to know the target CGI and says nothing about failure modes, which is the main remaining gap.

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 100%, so url/form/query/method are already documented; the description adds real value only for url, explaining that a bare 'host/path' is dispatched via the h5.qzone.qq.com proxy and giving a concrete example. form, query and method get no extra explanation beyond the schema.

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

Purpose5/5

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

States a specific verb and resource ('call any QQ空间 web CGI'), and the parenthetical '(escape hatch)' immediately distinguishes it from the many dedicated qzone_* siblings that wrap specific endpoints. The added detail that cookies and g_tk are injected automatically tells the agent this is the authenticated raw-request path, not a normal API.

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?

'escape hatch' implies use only when a dedicated tool does not cover the endpoint, but the description never states that condition explicitly nor names any alternative. The url examples clarify accepted formats rather than when to reach for this tool over get_qzone_feeds, comment_qzone, and the rest.

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