Skip to main content
Glama

get_qzone_share_ark

Generate a QQ Zone feed share card from a complete feed object, returning the original content and share hint without sending a message.

Instructions

生成空间动态分享卡片,返回原文及分享提示 feed 原样取自 get_qzone_feed_detail 的 feed,或 get_qzone_home_feeds / get_qzone_public_feeds 的 feeds 条目。分享链接可能允许未登录者访问并包含作者 QQ 号;如 requires_confirmation=true,发送前展示 notice 并取得确认。将 ark 原文作为 JSON 消息发送,不要修改卡片内容。 Returns: 生成卡片但不发送消息;后续发送仍返回普通消息编号。

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": {
      "feed": "<feed>"
    },
    "name": "get_qzone_share_ark"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedYes主页、详情或推荐列表返回的完整动态,保留所有原始字段

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false) get meaningful reinforcement: the description discloses that the share link may be reachable by unauthenticated users and embeds the author's QQ number, that a confirmation notice must be shown, and that the card content must not be altered. It also clarifies the return is only the card, with the actual send yielding an ordinary message id. The privacy/open-world implications are unusually well surfaced.

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?

Purpose is front-loaded and every sentence carries operational content (source, privacy caveat, confirmation gate, immutability, return semantics). It is dense and mixes Chinese and English labels like 'Returns:', but there is no filler to cut.

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?

With a nested free-form object parameter and no output schema, the description does the necessary work by explaining where the object comes from and what the call yields. Slightly more detail on the shape of the returned share hint/ark would close the remaining gap, but nothing critical for correct invocation is missing.

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?

Schema coverage is 100% and the single feed property is already documented as the full feed object with all original fields preserved. The description adds genuine provenance semantics — which upstream tools produce a valid feed and that it must be passed through unmodified — which the schema alone does not convey.

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?

The opening clause states a specific verb and resource: generate a Qzone feed share card and return the original text plus a share hint. It then distinguishes itself from the send-side siblings by saying the card is generated but no message is sent, so an agent can tell it apart from send_ark_share / send_group_ark_share without opening schemas.

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?

It tells the agent exactly where the feed argument must come from (the feed from get_qzone_feed_detail, or an entry from get_qzone_home_feeds / get_qzone_public_feeds) and gives a conditional procedure when requires_confirmation=true. It does not name the sending tool explicitly as the follow-up alternative, leaving that step implicit.

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