Skip to main content
Glama

get_qzone_public_capabilities

Read-only

Retrieve the current QQ account's Qzone public entry and push permissions to inspect available capabilities, preserving unknown response fields.

Instructions

读取当前账号的空友爱看入口与推权限 Returns: 当前账号的上游入口能力对象,保留未知字段。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior: it returns an upstream entry-capability object and unknown fields are preserved (forward-compatibility guidance). It does not mention auth requirements, whether results are cached, or whether the call can fail for accounts without the entry enabled.

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?

A single sentence plus an inline 'Returns:' clause, front-loaded with the read action and resource. No filler. The inline 'Returns:' label is slightly abrupt but does the structural job efficiently.

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 must carry return-value meaning, and it does so only at the type level ('上游入口能力对象,保留未知字段') without naming any fields of the capability object. For a zero-parameter read tool this is close to adequate, but an agent cannot predict what keys to expect or how to interpret a missing/disabled entry.

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, which is the baseline-4 case, and the empty schema with additionalProperties=true matches that. The description correctly adds no parameter guidance and focuses on return semantics instead.

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 uses a specific verb (读取/read) applied to a specific resource: the current account's 空友爱看入口 (public-feed entry) and 推权限 (push permission) capability object. An agent can tell this apart from the feed/comment/reply siblings, which all operate on content rather than account capability. The only weakness is that the domain jargon ('入口能力') is not glossed, so the exact scope of 'capability' relies on naming alone.

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 statement of when to call this versus the many get_qzone_* content tools, and no prerequisites or exclusions. The agent must infer that this is a pre-flight capability/permission probe. Nothing in the text rules out misuse.

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