Skip to main content
Glama
Sign In
coolapk-mcp-pro

coolapk-mcp-pro

by yufeng-liang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

coolapk_image_link

Converts Coolapk image URLs into signed, expiring HTTPS links hosted on the MCP server so chat clients can display images directly without anti-hotlink errors.

Instructions

把酷安图片地址转成可直接在聊天窗口显示的 https 链接（需远程 HTTP 部署）。

为什么需要它：酷安 image.coolapk.com 对非酷安客户端返回 HTTP 567（防盗链）， 很多聊天类客户端又没有解码 base64 的能力，只能显示文字链接。此工具把图片 转成托管在 MCP 服务上的签名链接（/img），链接自带过期时间与 HMAC 签名， 任何能打开网页的客户端都能直接显示图片。

仅在远程 HTTP 模式可用：MCP 进程需配置 COOLAPK_PUBLIC_BASE（对外访问前缀， 例如 https://mcp.example.com）与 COOLAPK_HTTP_TOKEN（用作签名密钥）。

Args: urls: 一个或多个酷安图片 URL，用逗号、空格或换行分隔 ttl_minutes: 链接有效期（分钟），默认 120，最长 10080（7 天）

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": {
      "urls": "<urls>"
    },
    "name": "coolapk_image_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYes
ttl_minutesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the upstream 567 hotlink block, that links are HMAC-signed and self-expiring, and that COOLAPK_PUBLIC_BASE/COOLAPK_HTTP_TOKEN must be configured. It does not state what error/behavior occurs when deployed in stdio mode, leaving that inference to the agent.

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?

Front-loads the action, then justifies it with the hotlink/base64 problem before covering deployment prerequisites. Slightly long with a dedicated 'why' section and Args block, but every part contributes usable information.

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 2-parameter tool with an output schema, the description covers purpose, prerequisites, parameter formats, and the expiry semantics. The only gap is sibling differentiation and failure behavior outside remote mode.

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

Parameters5/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 supply all parameter meaning, and it does: urls accepts multiple URLs separated by comma, space, or newline, and ttl_minutes has a default of 120 and a hard cap of 10080. Both parameters are fully specified beyond the bare titles in the schema.

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?

States a specific verb and resource: converts Coolapk image URLs into HTTPS links hosted on the MCP service. The mechanism (signed /img links) is concrete, but it never names or contrasts itself with siblings like coolapk_read_image or coolapk_get_url, which also deal with retrieving images/URLs.

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?

Explains the triggering condition well: use it when a chat client cannot decode base64 and needs a directly renderable link, and it is only usable under remote HTTP deployment. It does not explicitly say 'use coolapk_read_image instead when X', so the alternative routing is left implicit.

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