Skip to main content
Glama
Grinv

MAL MCP Server

by Grinv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get anime genres

get_anime_genres
Read-only

List anime genres, themes, and demographics with their MAL IDs so you can find the numeric values search_anime’s genres parameter expects, with optional SFW filtering.

Instructions

List anime genres/themes/demographics with their MAL IDs. Use this to discover the numeric IDs that the genres parameter of search_anime expects. sfw/sfw_strict drop the adult (and, for sfw_strict, Ecchi) genres from the list itself.

Input Schema

NameRequiredDescriptionDefault
sfwNoIf true, exclude adult/explicit-rated entries (R+ Mild Nudity and up). Defaults to false (no filtering). Note: this alone still allows mainstream, safely-rated shows tagged with the Ecchi genre (fanservice) through — use `sfw_strict` to also exclude those.
filterNoRestrict to one kind of tag. Omit to list all.
sfw_strictNoIf true, exclude adult/explicit-rated entries AND anything tagged with the Ecchi genre, even otherwise-mainstream/safely-rated shows. Stricter than `sfw` alone. Defaults to false.

Output Schema

NameRequiredDescriptionDefault
genresYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.11.0
    • addedInput schema / properties / sfw
      Added value: +{
+  "description": "If true, exclude adult/explicit-rated entries (R+ Mild Nudity and up). Defaults to false (no filtering). Note: this alone still allows mainstream, safely-rated shows tagged with the Ecchi genre (fanservice) through — use `sfw_strict` to also exclude those.",
+  "type": "boolean"
+}
    • addedInput schema / properties / sfw_strict
      Added value: +{
+  "description": "If true, exclude adult/explicit-rated entries AND anything tagged with the Ecchi genre, even otherwise-mainstream/safely-rated shows. Stricter than `sfw` alone. Defaults to false.",
+  "type": "boolean"
+}
  2. Changed7 schema fields changedv0.9.0
    • addedOutput schema / properties / genres / items / properties / count / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / genres / items / properties / count / minimum
      Added value: +0
    • changedOutput schema / properties / genres / items / properties / count / type
      Previous value: -"number"New value: +"integer"
    • addedOutput schema / properties / genres / items / properties / mal_id / exclusiveMinimum
      Added value: +0
    • addedOutput schema / properties / genres / items / properties / mal_id / maximum
      Added value: +9007199254740991
    • changedOutput schema / properties / genres / items / properties / mal_id / type
      Previous value: -"number"New value: +"integer"
    • addedOutput schema / properties / genres / items / required
      Added value: +[
+  "mal_id"
+]
  3. Changed1 schema field changedv0.8.0
    • addedInput schema / additionalProperties
      Added value: +false
  4. Changed2 schema fields changedv0.7.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "genres": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "count": {
+            "type": "number"
+          },
+          "mal_id": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "genres"
+  ],
+  "type": "object"
+}
  5. Addedv0.2.0

TDQS

A4/5.0
Behavior3/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 adds that sfw/sfw_strict drop genres from the list itself, which is a useful behavioral clarification about output rather than input filtering. It says nothing about result size, caching, or ordering, so the added context is modest.

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?

Three short sentences, zero waste, front-loaded with what is returned and immediately followed by the reason to call it. No redundancy with the schema beyond a brief needed clarification.

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?

The output schema exists, so return values need not be described. Purpose, cross-reference to search_anime, and filter semantics are all present, making the definition sufficient for correct invocation. A minor gap: no hint that omitting `filter` returns all four tag kinds in one payload.

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

Parameters3/5

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

Schema description coverage is 100%, and each parameter already carries a detailed explanation of the sfw vs sfw_strict distinction. The description's restatement of those flags adds only slight value (clarifying that whole genres disappear from the returned list), so the schema continues to do the heavy lifting.

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 anime genres/themes/demographics with their MAL IDs') and names the taxonomy kinds it covers. This clearly distinguishes it from the sibling get_manga_genres and from search_anime without needing the schema opened.

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?

Explicitly routes the agent: use this to discover the numeric IDs that the `genres` parameter of search_anime expects. It covers the main case and the alternative, but gives no when-not-to-use condition (e.g., that a free-text search may be faster if the genre name is already known).

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

Deploy Server

Other Tools