Skip to main content
Glama
ComicK MCP Server

ComicK MCP Server

by edmer664

get_comic_chapters

Retrieve paginated chapter listings for a ComicK comic using its slug or hid, with optional language filtering.

Instructions

List chapters for a comic on ComicK. Accepts either the comic's slug or hid.

Args: comic_id_or_slug: Comic slug or hid (auto-resolves slug to hid). lang: Language code filter (default "en"; comma-separated like "en,fr" or empty for all). page: 1-based page number (default 1). limit: Chapters per page (default 30, max 100).

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": {
      "comic_id_or_slug": "<comic_id_or_slug>"
    },
    "name": "get_comic_chapters"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen
pageNo
limitNo
comic_id_or_slugYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/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 disclosure burden and does add real behavior: slug-to-hid auto-resolution, the default language, 1-based paging, and a hard cap of 100 chapters per page. It does not address error behavior for an unknown comic or whether results are ordered, but the operational details it does give go beyond the bare schema.

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 is front-loaded in the first sentence, followed by a compact Args block that maps one line per parameter with no filler. The formatting is easy to scan; the only mild redundancy is restating defaults already present in the schema.

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 read-only paginated list tool with four parameters and an output schema that already defines return values, this is nearly complete: identifier handling, language filtering, paging, and limits are all covered. The remaining gap is guidance on behavior when the comic is not found or the chapter list is empty.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate, and it does for all four parameters: comic_id_or_slug accepts slug or hid, lang takes a comma-separated list or empty for all, page is 1-based, and limit caps at 100. Only minor gaps remain, such as the accepted language-code format beyond examples like 'en,fr'.

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 opens with a specific verb and resource: 'List chapters for a comic on ComicK,' which clearly separates it from get_comic_details and the search/recommendation siblings. It also states the two accepted identifier forms, so an agent can tell exactly what this tool returns versus the detail tool. It stops short of explicitly naming a sibling to contrast with.

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 'list chapters for a comic' framing implies when to reach for this tool, and the slug-or-hid note clarifies the entry condition. However, there is no explicit when-not guidance and no mention of alternatives such as get_comic_details for metadata versus this tool for chapter listings.

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