Skip to main content
Glama

share_peer

Read-only

Generates a QQ contact or group share Ark card from a user ID, group ID, or phone number and returns the card JSON without sending it to a chat.

Instructions

分享用户/群 Ark 卡片 生成联系人分享卡片;返回卡片数据,不等同于发送到聊天。 Returns: { arkMsg }:服务端生成的推荐联系人 Ark 卡片 JSON 字符串。

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": "share_peer"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idNo
group_idNo
phone_numberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description usefully reinforces that the tool only produces card data and performs no send action, which is the main behavioral risk an agent would worry about. It also sketches the return payload, going beyond what the annotations say, though it says nothing about auth or rate limits.

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 compact sentences plus a short return-value clause, with the not-a-send caveat placed early where it matters most. There is minor redundancy between '分享用户/群 Ark 卡片' and '生成联系人分享卡片', but nothing 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?

With no output schema, the description correctly supplies the return shape ({ arkMsg } as a server-generated JSON string), and the read-only nature is covered. However, for a three-parameter tool with zero schema documentation, the missing identifier semantics leave a real gap in calling it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters (user_id, group_id, phone_number), so the description carries the full burden and largely fails. Mentioning 'user/group' hints at user_id and group_id, but it never explains phone_number, which identifier wins when several are supplied, or that all three are optional.

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 definition gives a specific verb and resource: it generates a contact share Ark card for a user or group. It also draws a clear boundary by stating the result is card data, not a message sent to chat. The one weakness is that it oscillates between 'user/group Ark card' and 'recommended contact card', which slightly muddies the scope.

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?

The phrase '不等同于发送到聊天' explicitly tells the agent when NOT to use this tool, which is the key fork against the send_ark_share / send_group_ark_share siblings. It stops short of naming a replacement tool or stating prerequisites, so the routing guidance is clear but not complete.

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