noyacg-mcp

漫画详情（含章节与首屏评论）

noy_book_detail

Read-only

Get a manga's full details—title, author, tags, synopsis, rating, favorites, categorized chapters, price, similar titles, and initial comments—by book ID.

Instructions

读取一部漫画的完整资料：书名、作者、标签、简介、评分、收藏、章节列表（按分类）、售价、同类推荐，以及首屏评论和评论总数。章节列表已经内联在详情里，不需要单独请求；想看更多评论用 noy_book_comments。注意：这是 GET 接口（社区那套是 POST），并且未登录会返回 status: login。

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_detail"
  }
}

Input Schema

Name	Required	Description
`bid`	Yes	书籍 ID（Bid，例如 54485）
`adult`	No	是否请求成人向内容（allow-adult 请求头）。不传则用环境变量 NOY_ALLOW_ADULT，默认 false。注意 /api/home 的服务端默认值是 true（不带就是 R18），本项目会显式传 false。
`comment_limit`	No	展示多少条评论（0 = 只显示条数）

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 29, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuinely new behavioral facts: this is a GET endpoint unlike the POST-based community API, and an unauthenticated call yields `status: login` rather than data. It stops short of describing failure modes beyond login or response shape, keeping it below a 5.

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?

Three short, front-loaded sentences: payload contents first, then the inlining/alternative routing, then the transport/auth caveat. The long field enumeration is dense but each item maps to actual returned data; only minor trimming is possible.

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 no output schema, the description carries the return-value burden and does so by enumerating the payload, and it covers the key auth pitfall. It could still say more about what `status` values mean or how comments are truncated, but nothing essential to calling it correctly is missing.

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 description coverage is 100% and the `bid`, `adult`, and `comment_limit` descriptions already explain IDs, the allow-adult header fallback, and the 0–20 comment cap. The description adds nothing parameter-level beyond what the schema states, so the baseline 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?

States a specific verb (读取) and resource (一部漫画的完整资料) and then enumerates the exact payload: title, author, tags, synopsis, rating, favorites, chapter list by category, price, recommendations, first-screen comments and comment count. It also explicitly distinguishes itself from the sibling noy_book_comments, so an agent can route without opening either schema.

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?

Explicitly tells the agent that the chapter list is already inlined and no separate request is needed, and that noy_book_comments is the tool for more comments — a named alternative plus the condition that selects it. It also flags the transport/auth caveat (GET vs the community POST set; unauthenticated returns `status: login`), which is usage-relevant pre-call information.

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