Skip to main content
Glama

share_group_ex

Read-only

Generates a QQ group recommendation Ark card as JSON for sharing, returning card data without sending it to a chat; provide group_id to build the shareable card payload.

Instructions

分享群 Ark 卡片 生成群分享卡片;返回卡片数据,不等同于发送到聊天。 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": "share_group_ex"
  }
}

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 already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false; the description goes beyond them by stating explicitly that nothing is sent to chat and that the result is a server-generated JSON string. It does not cover permissions, rate limits, or whether the generated card expires, which keeps it short of a 5.

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 core action and then the key disambiguation. The leading label '分享群 Ark 卡片' duplicates the title role and the 'Returns:' clause partially repeats the preceding sentence, but there is no padding beyond that.

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-only generator with no output schema, the description covers what it does, what it produces (JSON card string), and what it does not do (send). Only the group_id semantics and any prerequisite about the group being accessible are missing.

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 description coverage is 0%, so the description must carry the burden for group_id, and it says nothing about it — no format, no whether numeric or string ID is preferred despite the union type. The parameter name is self-evident in context, which keeps this adequate rather than deficient.

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 pairs a specific verb (生成/generate) with a specific resource (群分享卡片/group share card) and adds the crucial qualifier that it only returns card data and is not the same as sending to chat. That distinguishes it functionally from send-like siblings such as send_group_ark_share, though no sibling is named.

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?

It supplies a clear negative guideline ('不等同于发送到聊天'), which tells the agent this is a preparation step rather than a delivery action. There is no positive when-to-use statement and no named alternative for the actual sending case, so routing is only implied.

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