Skip to main content
Glama

send_tuwen_ark

Sends an image-text Ark share card to a QQ private or group chat using a title, description, and jump URL.

Instructions

发送图文 Ark 卡片(私聊/群聊) 替换目标群号及实际链接;会发送分享卡片。 Returns: null

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": {
      "title": "<title>",
      "desc": "<desc>",
      "jump_url": "<jump_url>"
    },
    "name": "send_tuwen_ark"
  }
}

Input Schema

NameRequiredDescriptionDefault
descYes
titleYes
summaryNo[分享]
user_idNo
group_idNo
jump_urlYes
preview_urlNohttps://tangram-1251316161.file.myqcloud.com/files/20210721/e50a8e37e08f29bf1ffc7466e1950690.png

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds two genuinely useful facts beyond that – the tool produces a share-card message and returns null (nothing meaningful) – but says nothing about permissions, rate limits, or what happens if both user_id and group_id are supplied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, so there is little waste, but the phrasing reads like a leftover template instruction ('replace target group number and actual link') spliced with a return-value note, making it hard to parse. Front-loading the purpose is fine; the rest is disorganized rather than efficiently compressed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is an open-world mutating send tool with 7 undocumented parameters and no output schema, so the description needs to do real work. It covers only the barest notion of the payload and omits target-selection semantics and parameter meanings entirely.

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 7 parameters, so the description must carry the burden and largely fails. It hints that a group number and a real link get substituted, but never explains title, desc, summary, preview_url, or the mutual exclusivity of user_id and group_id.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource (send an image-text Ark card) and adds scope (private chat / group chat). However, it does not distinguish this tool from the very similar sibling names such as send_ark_share and send_group_ark_share, and the closing note that it 'will send a share card' muddies the boundary further rather than sharpening it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool rather than the ark/share siblings, nor when to choose the user_id path versus the group_id path. The parenthetical '(private chat/group chat)' implies both targets are supported but gives no selection rule or prerequisites.

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