Skip to main content
Glama
Grinv

MAL MCP Server

by Grinv
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Get anime genres

get_anime_genres
Read-only

Fetch anime genres, themes, and demographics with their MAL IDs. Use these numeric IDs to filter search results via the genres parameter.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNoRestrict to one kind of tag. Omit to list all.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
genresYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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"
+]
  2. Changed1 schema field changedv0.8.0
    • addedInput schema / additionalProperties
      Added value: +false
  3. 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"
+}
  4. Addedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. Description adds that it lists items with MAL IDs, providing behavioral context beyond annotations.

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, no wasted words. Front-loaded with action and purpose. Concisely conveys what the tool does and why to use it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description doesn't need to explain return values. It fully covers the tool's purpose and usage for its simple parameter set.

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 has 100% coverage on the single parameter, including enum and description. Description does not add extra meaning beyond what the schema already provides, so baseline 3 is appropriate.

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?

Clearly states it lists anime genres/themes/demographics with MAL IDs, and distinguishes its purpose from sibling by explaining it supplies IDs for search_anime's `genres` parameter.

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 says when to use this tool (to discover genre IDs for search_anime). It does not exclude other uses but provides clear context, though it could mention alternative for manga (get_manga_genres).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Grinv/mal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server