Skip to main content
Glama
coolapk-mcp-pro

coolapk-mcp-pro

by yufeng-liang

coolapk_notify

查看通知(@我的、评论、点赞、关注、私信)。

Instructions

查看通知(@我的、评论、点赞、关注、私信)。

适合「有人回复我了吗」「私信里说了什么」这类需要个人时间线的场景; 只读,不会标记已读或回复。

Args: ntype: 通知类型,可选 atMeMeFeed(@我的动态) atComment(@我的评论) comment(评论) feedLike(点赞) contactsFollow(关注) message(私信), 默认 message page: 页码,默认 1 with_count: 是否附带各类型未读/总数统计(多一次请求)

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

Input Schema

NameRequiredDescriptionDefault
pageNo
ntypeNomessage
with_countNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose the key traits: it is read-only, does not mutate read state, and cannot send replies. It also warns that with_count costs an extra request, which is genuine behavioral context; it omits any mention of login/auth requirements or per-page limits.

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?

Purpose and usage scenarios are front-loaded in two tight sentences, followed by a conventional Args block. There is minor redundancy restating defaults (page=1, ntype=message) that already exist in the schema, but no sentence is padding.

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 shape need not be described, and the three-parameter surface is fully explained, making the definition complete for correct invocation. The remaining gap is operational context an agent might want: whether authentication is required and how pagination terminates or what page size applies.

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% and the schema exposes no enum for ntype, yet the description enumerates every valid ntype value with a Chinese gloss for each and states the default (message). It also explains page as 页码 with default 1 and clarifies that with_count adds per-type unread/total counts at the cost of one extra request — meaning well beyond the bare 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?

The opening line gives a specific verb and resource (查看通知) and enumerates the covered notification kinds (@我的、评论、点赞、关注、私信), so the agent knows exactly what data this returns. The parenthetical '个人时间线' framing separates it from the public-feed siblings such as coolapk_home or coolapk_user_feeds.

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?

It supplies concrete use-case triggers ('有人回复我了吗'、'私信里说了什么') that map cleanly onto when to call it, and adds a negative boundary by stating it will not mark items read or reply. It stops short of naming an alternative tool or giving exclusion conditions, so it is strong but not complete routing guidance.

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