Skip to main content
Glama

qzone_forward

Forward a QQ Zone post to your own space with an optional comment by providing the author UIN and post TID.

Instructions

转发 a 说说 to your own 空间, with an optional comment.

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": {
      "uin": "<uin>",
      "tid": "<tid>"
    },
    "name": "qzone_forward"
  }
}

Input Schema

NameRequiredDescriptionDefault
tidYes说说 tid
uinYesAuthor of the 说说
contentNoYour comment on the forward

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, open-world, non-destructive write, and the description usefully adds that the result lands in the caller's own 空间 with an optional comment. It does not disclose whether the original content is embedded, whether permissions on the source 说说 are required, or what a failure looks like.

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?

One short, front-loaded sentence with no filler; the destination phrase appears before the optional-comment clause. The mixed Chinese/English phrasing is slightly awkward but not wasteful.

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?

For a 3-parameter write tool with full schema coverage and annotations present, the description covers the essential action and target. It stops short of the behavioral details that matter for a cross-account repost, such as source-visibility requirements or what the forwarded post contains.

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 tid, uin, and content are already documented in the schema. The description adds only that the comment is optional, which is already conveyed by the default empty string; no extra meaning about uin formatting or tid sourcing is provided.

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 gives a concrete verb ('转发') and resource ('说说') plus the destination ('your own 空间'), so the agent knows this creates a repost rather than a plain comment or message forward. It does not distinguish itself from the sibling 'forward_qzone_public_feed', leaving ambiguity about which forwarding target to pick.

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 when-to-use or when-not-to-use guidance and no prerequisites stated (e.g., whether the caller must be able to view the original 说说). The presence of a similarly named sibling makes the absence of routing guidance a real gap.

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