Skip to main content
Glama
Sign In
JMComic AI

JMComic AI

by hect0x7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_album_comments

Retrieve a page of comments for a manga album, including nested replies and spoiler indicators.

Instructions

获取本子的一页评论，包括递归回评和剧透标识。

参数: album_id: 本子 ID (例如 "302820")。 page: 评论页码，从 1 开始（默认值：1）。

返回: 包含以下内容的字典： - album_id: 本子 ID - page: 当前页码 - page_size: 每页主评论数量 - total: 全部分页的主评论总数；不可用时为 null - page_count: 总页数；不可用时为 null - comment_count: 当前页主评论与所有层级回评总数 - comments: 评论列表，每条评论包含 replies 和 is_spoiler

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": {
      "album_id": "<album_id>"
    },
    "name": "get_album_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
album_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure; it usefully explains pagination, recursive replies, spoiler flags, and null behavior for total/page_count. However, it does not state authentication needs, read-only guarantees, or error behavior for invalid album_id/page.

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 opening sentence is front-loaded and the parameter/return sections are clearly structured and reasonably compact. A minor deduction: the detailed return field list overlaps with the available output schema, adding length beyond the strict minimum.

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?

For a low-complexity, two-parameter read tool, the description covers purpose, parameter semantics, and return semantics including nullability. It lacks usage-routing context relative to sibling tools, which is the main completeness gap.

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 description fully compensates by explaining album_id's identity with an example and page's 1-based, defaulted value. This adds meaning the input schema alone cannot provide.

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 description states a clear action ('获取本子的一页评论') with the album/comments resource and scope, and adds distinctive features of recursive replies and spoiler flags. It does not explicitly contrast with the sibling get_forum_comments, so it falls just short of full differentiation.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this tool over alternatives such as get_forum_comments or when paginated access is needed. The description implies the use case through its name and wording, but does not state exclusions or alternatives.

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