Skip to main content
Glama

send_group_ark_share

Read-only

Generate a QQ group recommendation Ark card as JSON for a specified group_id, returning card data for later sharing without sending it to chat.

Instructions

分享群 Ark 卡片(NapCat 标准名) 生成群分享卡片;返回卡片数据,不等同于发送到聊天。 Returns: 服务端生成的群推荐 Ark 卡片 JSON 字符串。

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": {
      "group_id": "<group_id>"
    },
    "name": "send_group_ark_share"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, and the description reinforces this with the crucial clarification that despite the send_ prefix nothing is delivered to the chat — a real gotcha this definition defuses. It also discloses the return is a server-generated JSON string, adding value beyond the annotations.

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?

Short and front-loaded, with the non-sending caveat placed before the return note. The return value is stated twice across the Chinese and English clauses, which is mild redundancy but not wasteful.

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, no-output-schema tool, the definition covers the one behavior an agent could get wrong (assuming it sends a message) and states the return type. Missing group_id format expectations and any indication of what the card JSON contains are minor residual gaps.

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?

With one parameter at 0% schema description coverage, the description carries the burden but says nothing about group_id beyond the field name; the minimum and integer|string union are left to the schema. The meaning of group_id is largely self-evident, so this is adequate rather than strong.

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 states a concrete action and resource — generating a group share Ark card and returning the card JSON rather than sending it. It is clear enough to separate this from chat-sending siblings, though it does not name a specific sibling such as send_ark_share to sharpen the distinction.

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?

The note that the result is card data and 'not equivalent to sending to chat' implies this is a preparatory/generation step, which guides usage. However, there is no explicit statement of when to choose this over send_ark_share or send_group_msg, leaving the agent to infer the follow-up flow.

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