Skip to main content
Glama
ComicK MCP Server

ComicK MCP Server

by edmer664

recommend_comics_by_prompt

Turns a natural-language request into ranked comic recommendations using genre and trope searches, verified tags, relevance scoring, and clear explanations.

Instructions

Recommend comics from ComicK for a conversational user request such as "I want a badass MC manhwa with swords and magic".

Runs multi-pass trope and genre searches, verifies MangaUpdates category tags on top candidates, scores relevance against genres, verified tags, synopses, ratings, and follower counts, and returns rich recommendations with explanations.

Args: prompt: Natural-language request describing what the user wants to read. limit: Number of recommendations to return (default 10, max 25). min_chapters: Optional minimum chapter count filter (e.g. 50). status: Optional publication status filter ('ongoing', 'completed', 'hiatus', 'cancelled').

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": {
      "prompt": "<prompt>"
    },
    "name": "recommend_comics_by_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
promptYes
statusNo
min_chaptersNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose real behavior: multi-pass trope/genre searches, MangaUpdates tag verification on top candidates, and scoring across genres, tags, synopses, ratings and follower counts, plus that results come with explanations. What is missing is cost/latency framing for this heavyweight multi-pass pipeline and any note on behavior with sparse or zero matches.

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?

Front-loaded with a one-sentence purpose, then the pipeline, then a clean Args list, so an agent can stop reading early. Minor waste in restating limit's default of 10 already present in the schema, but the rest of the parameter notes earn their space.

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 4-parameter, 1-required tool with no annotations and an output schema, the description covers purpose, ranking pipeline, and every parameter's meaning and constraints. It does not say what happens when nothing matches or whether status accepts only those exact lowercase strings, which keeps it from being fully complete.

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 coverage is 0%, so the Args block does all the work, and it delivers: prompt is a natural-language request, limit has a default of 10 and a max of 25 not present in the schema, min_chapters is explained with an example, and status enumerates the four accepted values that the schema leaves as a bare string. This is exactly the semantics the structured fields omit.

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?

States a specific verb and resource ('Recommend comics from ComicK') and scopes it to conversational requests, with a concrete example query. The multi-pass search plus tag-verification pipeline implicitly separates it from a plain keyword search like search_comics, but it never names or explicitly contrasts a sibling.

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

Usage Guidelines4/5

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

The description makes the usage context clear: it is for natural-language requests such as 'I want a badass MC manhwa with swords and magic', implying conversational intent rather than exact-title lookup. It stops short of explicit exclusions, e.g. telling the agent to prefer search_comics for a known title or get_comic_details for a known ID.

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