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

coolapk-mcp-pro

by yufeng-liang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

coolapk_read_image

Downloads Coolapk CDN images—such as post images and avatars—and returns them as image content so you can view Coolapk-hosted media; only permitted image domains are accepted.

Instructions

下载酷安 CDN 图片并作为图片返回（用于查看动态配图、头像等）。

仅允许酷安图片域名：image.coolapk.com / avatar.coolapk.com / static.coolapk.com。失败时返回结构化错误，可改用 coolapk_get_url 获取接口数据，或直接向用户呈现 URL。

Args: url: 图片完整 URL（http 自动升级 https）

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": {
      "url": "<url>"
    },
    "name": "coolapk_read_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the load well: it discloses the domain allowlist (image/avatar/static.coolapk.com), automatic http→https upgrade, and structured errors on failure. It does not mention size limits, auth needs, or exactly how the image payload is delivered, but the core behavioral contract is present.

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-loaded with purpose, then constraints, then fallbacks, then the arg. Efficient overall, though the Args block partially repeats the domain/https info already stated above.

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 one-param image fetch with no annotations or output schema, the description covers what it returns (an image), domain restrictions, error behavior, and alternatives. Remaining gaps (payload size limits, whether the image is inlined or referenced) are minor.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate, and it does: the single 'url' param is defined as the full image URL with http auto-upgraded to https and restricted to specific Coolapk domains. This is substantive meaning beyond the bare 'string' schema.

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

Purpose5/5

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

States a specific verb+resource (download Coolapk CDN image and return it as an image) plus the concrete use cases (feed images, avatars). It also implicitly separates itself from coolapk_image_link / coolapk_get_url by emphasizing that it returns image content rather than link/API data.

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?

Gives clear usage context (viewing post images and avatars) and explicit fallback guidance: on failure switch to coolapk_get_url or show the URL to the user. It does not explicitly contrast with the sibling coolapk_image_link, which is the most plausible alternative an agent would weigh.

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