Skip to main content
Glama

webtoon_genres

Read-only

List WEBTOON's complete 17-genre taxonomy with each genre's slug, display label and listing URL. Use this first to get a valid genre slug for webtoon_genre; do not hard-code the set, and note that three slugs are underscored (graphic_novel, slice_of_life, super_hero).

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": "webtoon_genres"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description still contributes real behavioral detail beyond that: the taxonomy size, the returned fields, and the warning that three slugs use underscores (graphic_novel, slice_of_life, super_hero), which prevents malformed downstream calls.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose then routing guidance then the slug caveat. No filler, and the exception about underscored slugs is placed where it will be read before acting.

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 explained, and the read-only nature is covered by annotations. The description covers everything an agent needs to call it and use the result; only a statement of stability or freshness of the taxonomy is absent, which is minor.

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?

The tool takes zero parameters, so the baseline is 4. No parameter meaning is needed, and the description correctly spends its words on output shape instead.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List WEBTOON's complete 17-genre taxonomy') plus what each entry contains (slug, display label, listing URL), and the count gives a concrete scope. It is clearly distinguishable from webtoon_genre, which takes a slug this tool supplies.

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

Usage Guidelines5/5

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

Explicitly says 'Use this first to get a valid genre slug for webtoon_genre' and warns 'do not hard-code the set', which is both a when-to-use rule and an ordering constraint relative to a named sibling.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.