Skip to main content
Glama
ComicK MCP Server

ComicK MCP Server

by edmer664

get_comic_details

Retrieve a ComicK entry's metadata, synopsis, genres, verified tags, authors, artists, ratings, and similar recommendations by slug or ID.

Instructions

Retrieve full metadata, synopsis, genres, verified MangaUpdates tags/categories, authors, artists, ratings, and similar comic recommendations for a ComicK entry.

Args: comic_id_or_slug: Comic slug (e.g. "01-survival-story-of-a-sword-king-in-a-fantasy-world") or hid (e.g. "Qy66f_CI").

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

Input Schema

NameRequiredDescriptionDefault
comic_id_or_slugYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a read-only lookup by its field enumeration, but never states that it is non-mutating, what happens when the slug is invalid or ambiguous, whether the call is rate-limited, or if it requires any auth. This is a meaningful gap for an unannotated tool, though the enumeration of returned fields adds some value.

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 purpose sentence is front-loaded and the Args block is short and scannable with no filler. The field enumeration is long but each item conveys real information about the payload; the only minor waste is repeating return contents that the output schema may already cover.

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 one-parameter lookup with an output schema present, most of what an agent needs is here: what it fetches and exactly what identifier formats are accepted. The missing pieces relative to an unannotated tool are failure behavior on bad identifiers and routing guidance versus search_comics.

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 fully document the single parameter — and it does, explaining that the value is either a Comic slug or a hid and giving a concrete example of each format ("01-survival-story-of-a-sword-king-in-a-fantasy-world" vs "Qy66f_CI"). It stops short of saying whether a numeric ComicK id is also accepted, which leaves a residual ambiguity.

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 uses a specific verb ('Retrieve') and names the resource precisely, enumerating the payload (metadata, synopsis, genres, MangaUpdates tags, authors, artists, ratings, recommendations) and scoping it to 'a ComicK entry'. This clearly separates it from catalog-browsing siblings like get_trending_comics, though it never names a sibling or states an explicit contrast.

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?

Usage is only implied: the presence of a single slug/hid argument signals 'call this when you already have an identifier'. There is no statement of when to prefer search_comics first, no prerequisite telling the agent it must resolve a slug via search, and no exclusion guidance.

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