Skip to main content
Glama

get_mini_app_ark

Read-only

Converts Bilibili or Weibo mini-app card ARK data into an actual share URL and returns the card object without sending it.

Instructions

获取小程序卡片 ark 替换为实际分享地址;当前仅支持 bili 和 weibo。返回的 data 是卡片对象,不会自动发送。

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

Input Schema

NameRequiredDescriptionDefault
descNo
typeNo
titleNo
picUrlNo
jumpUrlNo
pic_urlNo
jump_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true. Beyond that, the description adds real behavioral information: the result is placed in `data` as a card object and is not dispatched automatically, plus the platform support limit for bili/weibo. What it omits is any failure mode (e.g., what happens for an unsupported platform).

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 the constraint plus return caveat follow logically. Nothing is padding, though the mixed terminology ('ark', '卡片对象') assumes prior domain knowledge that costs a little clarity.

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?

With 7 undocumented parameters, no output schema and a mutation-adjacent data-shaping role, the description covers only the return payload and the platform limit. It gives no guidance on which of the duplicate field spellings to use or what the input shapes mean, which is the biggest gap for an agent trying to call this 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?

There are 7 parameters at 0% schema description coverage, including duplicated pairs (picUrl/pic_url, jumpUrl/jump_url) that an agent cannot disambiguate without help. The description explains none of them; only the implicit 'type' constraint (bili/weibo) is hinted at, leaving the schema's real ambiguity entirely unresolved.

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: fetch a mini-program card 'ark' and resolve it into the real share URL, scoped to bili and weibo. It is jargon-heavy ('ark'), but an agent familiar with the domain can tell what it retrieves, and '不会自动发送' implicitly separates it from the send_* siblings without naming them.

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 clause '不会自动发送' hints that a separate send tool is needed to actually deliver the card, and '当前仅支持 bili 和 weibo' gives a clear eligibility constraint. However, no sibling is named as the alternative and no explicit when-to-use/when-not-to-use rule is stated, so the guidance remains implied rather than directed.

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