Skip to main content
Glama

send_ark_share

Read-only

Generate a QQ user or group Ark share card as JSON for chat sharing; the result is returned to you and is not sent to a chat.

Instructions

分享用户/群 Ark 卡片(NapCat 标准名) 生成联系人分享卡片;返回卡片数据,不等同于发送到聊天。 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": "send_ark_share"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idNo
group_idNo
phone_numberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

The description adds meaningful behavior beyond the annotations by clarifying that this only generates and returns card data, not a chat message, and by naming the returned field arkMsg. This aligns with readOnlyHint=true and destructiveHint=false, and gives the agent the crucial side-effect expectation.

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?

The description is short and front-loads the core action and the important non-sending caveat. The return-value sentence is useful, though the bilingual phrasing adds slight redundancy.

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?

It adequately explains the return shape and the no-send behavior for a three-parameter tool, but with no output schema and zero parameter documentation, it omits important selection semantics for user_id, group_id, and phone_number.

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% and the description does not explain any of the three parameters. It does not clarify whether user_id, group_id, and phone_number are alternatives, which takes precedence, or what phone_number is used for, leaving the agent to guess.

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 specific action and resource: generating a contact/user or group Ark share card and returning the card JSON rather than sending it. It clearly distinguishes the return-data behavior from actual chat sending, though it does not explicitly contrast with the similarly named send_group_ark_share sibling.

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 key usage distinction is stated: the tool returns card data and is not equivalent to sending to a chat. However, it gives no explicit guidance on when to choose this over sibling card-generation tools or when to use user_id versus group_id.

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