noyacg-mcp

漫画评论列表

noy_book_comments

Read-only

Read paginated comments for a manga book by book ID, including nested replies and emoticon codes, and use the over flag to detect when the comment list ends.

Instructions

分页读取一部漫画下的评论（结构与帖子评论一致，但主键字段叫 cid 而不是 rid）。评论里的 [noygirl:yeah] 是表情包代码；楼中楼回复在 replies 里。用 over 判断是否到底。

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": {
      "bid": "<bid>"
    },
    "name": "noy_book_comments"
  }
}

Input Schema

Name	Required	Description
`bid`	Yes	书籍 ID（Bid）
`page`	No	页码，从 1 开始
`adult`	No	是否请求成人向内容（allow-adult 请求头）。不传则用环境变量 NOY_ALLOW_ADULT，默认 false。注意 /api/home 的服务端默认值是 true（不带就是 R18），本项目会显式传 false。
`limit`	No	返回多少条

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 29, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's main contributions are its return-structure disclosures: the primary key is `cid`, emoji codes appear as `[noygirl:yeah]`, nested replies live in `replies`, and `over` signals the end. These are genuinely useful for interpretation that annotations cannot convey, though nothing is said about auth or rate limits.

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?

The description is three dense sentences, and the core action (paginated comment reading for a book) is front-loaded. The cid-vs-rid caveat and the emoji-code note each earn their place.

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?

No output schema exists, so the description carries the burden of return shape, and it does so well by describing cid, replies, emoji codes, and the `over` terminator. What is missing is any note on authentication or on how `adult` interacts with the read, which would round it out.

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?

Schema coverage is 100%, so the schema already documents both bid, page, adult, and limit. The description adds no parameter-level detail and even introduces `over` (a response field) without tying it to limit or page semantics, so the baseline score of 3 applies.

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 description uses a specific verb (分页读取) and resource (一部漫画下的评论), and clarifies the difference in primary key naming (cid vs rid) from post comments, which is enough to distinguish it from the sibling noy_read_comment_replies.

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

Usage Guidelines3/5

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

The description implies pagination context through '用 `over` 判断是否到底' and notes that nested replies are returned in `replies`, but it never states when to call this tool instead of noy_read_comment_replies or noy_read_post. The guidance for choosing a tool is left implicit.

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