Skip to main content
Glama
coolapk-mcp-pro

coolapk-mcp-pro

by yufeng-liang

coolapk_board

浏览酷安板块(数码、二手、摄影、汽车、好物等 21 个板块)。

Instructions

浏览酷安板块(数码、二手、摄影、汽车、好物等 21 个板块)。

板块动态与首页动态是两套入口:想看「数码区最近在聊什么」「二手区的行情」 用这个工具,不要用 coolapk_home。板块 ID 见 boards 映射,常用: digital(数码) phone(手机) computer(电脑) system(系统ROM) sheying(摄影) meihua(美化) car(汽车) waishe(外设) goods(好物) kaixiang(开箱) secondhand(二手) secondhand_apple(二手苹果) hot(热榜) news(快讯) video(视频) wenda(问答) topic(话题) headline(头条) xianliao(闲聊) coolpic(酷图) newphone(新机)。

Args: board: 板块 ID(如 digital)、中文名(如 手机/数码/二手交易)或 page_name(如 V10_DIGITAL_HOME) page: 页码,默认 1

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": {
      "board": "<board>"
    },
    "name": "coolapk_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
boardYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. "Browse" implies a read-only, non-mutating operation, but nothing is said about pagination limits, whether more pages exist past the returned one, ordering, or auth requirements. The board-ID enumeration is useful context but is parameter data rather than behavioral disclosure.

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

Conciseness5/5

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

Purpose and the home-vs-board distinction are front-loaded in the first two lines, and the long ID list sits afterward where it can be skimmed. The 21-entry mapping is dense but each entry is load-bearing for a parameter that is otherwise undocumented.

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?

An output schema exists, so return values need no explanation, and both parameters are fully covered by the description. For a two-parameter read tool this is close to complete; only pagination termination and board-ID aliasing behavior are left implicit.

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%, and the description compensates well: it explains that board accepts a board ID, a Chinese name, or a page_name (V10_DIGITAL_HOME), and enumerates all 21 valid IDs with glosses. It also states page is a page number defaulting to 1. It stops short of noting invalid-board behavior or whether Chinese aliases are fuzzy-matched.

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 and resource (browse Kuai'an boards, 21 of them) and immediately differentiates itself from coolapk_home by framing boards vs. home as two separate entry points. An agent can tell what this returns without opening the schema.

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 an explicit when-to-use framing with example intents ("what is the digital board discussing", "second-hand market prices") and an explicit when-not (do not use coolapk_home). The gap is that sibling coolapk_secondhand and coolapk_topic overlap conceptually with the secondhand/topic boards, and the description does not say which entry point wins there.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.