Skip to main content
Glama
ComicK MCP Server

ComicK MCP Server

by edmer664

get_trending_comics

Retrieve trending, newly followed, or top-followed comics by format, ranking mode, and time window to identify popular titles and follow trends.

Instructions

Get trending, newly followed, or top-followed comics on ComicK.

Args: comic_type: Format type ('manhwa', 'manga', or 'manhua'). Default 'manhwa'. trend_type: Ranking mode ('trending', 'newfollow', 'follow'). Default 'trending'. days: Time window in days (7, 30, 90, or 180). Default 180. limit: Maximum number of results to return (default 15).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_trending_comics"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
limitNo
comic_typeNomanhwa
trend_typeNotrending

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 burden. It does disclose defaults (manhwa/trending/180/15) and the allowed value sets for days and comic_type, which is real added context, but it never states that results are read-only and ordered, nor does it mention pagination or any constraints on the time window.

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 tool purpose is front-loaded in a single sentence and the Args block is tight, one line per parameter. The literal 'Args:' formatting is slightly mechanical but nothing is redundant.

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?

An output schema exists, so return values need not be described, and all four untyped parameters are documented in the description. For a simple read-only listing tool this is nearly complete; ordering and whether days applies to 'follow' mode are the remaining gaps.

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 coverage is 0% and no enums are declared, yet the description documents all four parameters, including the permitted values for days (7/30/90/180) and comic_type (manhwa/manga/manhua) and the default for each. That compensates well; only the interaction between days and the non-trending modes is left unexplained.

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: 'Get trending, newly followed, or top-followed comics on ComicK', and the trend_type values make the three ranking modes explicit. It is clearly a ranked-listing tool rather than a search or detail lookup, though it never names a sibling like search_comics to sharpen the boundary.

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 implied by the parameter list: choose trend_type to pick a ranking mode and comic_type to pick a format. There is no explicit statement of when to prefer this over search_comics or recommend_comics_by_prompt, and no guidance on limits or rate behavior.

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