Skip to main content
Glama

get_qzone_profile

Read-only

Retrieve a QQ Zone profile's name and description for a specified QQ account, or the current account by default, when authorized.

Instructions

获取 QQ 空间名称和说明(默认当前账号) 需要有该空间的访问权限。 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_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
target_uinNo目标 QQ 号,省略则取机器人自己

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 structurally. The description adds a real behavioral constraint beyond that — the caller must have access permission to the target space — which is useful. It does not describe what happens on permission failure or what the returned text looks like when unset.

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 short sentences, front-loaded with the resource and the default scope. The trailing 'Returns: 空间名称和说明' largely repeats the opening clause, which is minor redundancy rather than bloat.

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 single-parameter read tool with full annotations and no output schema, the definition covers purpose, default scope, permission prerequisite, and the return content. Only the failure mode when access is denied is unaddressed.

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% and the single parameter already documents that omitting it targets the bot itself. The description restates that default but adds no format, range, or interpretation detail beyond the schema, so the baseline 3 applies.

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 plus resource — getting a Qzone's name and description — and implicitly contrasts with the sibling set_qzone_profile by being the read-side operation. It does not explicitly name an alternative, so it falls just short of 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'默认当前账号' tells the agent that omitting the target defaults to the bot's own account, and '需要有该空间的访问权限' states a prerequisite. There is no explicit when-not guidance or named alternative, but the usage context is clear.

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