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

coolapk-mcp-pro

by yufeng-liang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

coolapk_author

Evaluate a Coolapk author’s profile and authority score to determine if they are a domain expert before exploring more posts. Returns author tier, expert flag, fans-per-feed, and inferred expertise.

Instructions

查看酷安作者的画像与权威度评分（判断「这人是不是该领域大佬」）。

返回基础资料 + author_tier(top/expert/active/normal)、is_expert、 fans_per_feed(精发度)、expertise(从 bio 推断的专长领域)。 搜到高赞帖后先看作者 tier，再决定要不要用 coolapk_author_digest 深挖他的其他帖。

Args: uid: 用户UID

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": {
      "uid": "<uid>"
    },
    "name": "coolapk_author"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full load; it discloses the tier taxonomy (top/expert/active/normal) and flags that expertise is inferred from bio rather than declared, which is real behavioral context an agent needs to weigh reliability. It omits auth requirements, rate limits, and any failure modes for a nonexistent uid.

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?

The purpose is front-loaded followed by a compact list of return fields, then the workflow hint. The 'Args:' block is boilerplate but brief, so little is wasted.

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?

With an output schema present the description need not explain return values, yet it summarizes the most decision-relevant ones, and the sibling routing closes the loop for the follow-up step. The remaining gap is how an agent obtains a valid uid in the first place.

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

Parameters3/5

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

Only one parameter with 0% schema description coverage; the description adds little beyond restating 'uid: 用户UID', which the schema title already implies. It does not say where to obtain the uid (search results, feed detail) or that it must be the numeric Coolapk id.

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 definition names a specific verb+resource (查看酷安作者的画像与权威度评分) and enumerates the distinctive return fields (author_tier, is_expert, fans_per_feed, expertise), which separates it from the plain-profile siblings. It does not explicitly state how it differs from coolapk_user_profile, which overlaps on 基础资料, so it falls just short of a 5.

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

Usage Guidelines5/5

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

It gives an explicit trigger (搜到高赞帖后先看作者 tier) and an explicit alternative for the deeper case (coolapk_author_digest 深挖他的其他帖), so an agent knows both when to call this tool and what to call next.

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