Skip to main content
Glama
Grinv

MAL MCP Server

by Grinv
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Get manga characters

get_manga_characters
Read-only

Retrieve the character list and roles for any manga using its MyAnimeList ID from search_manga. See all characters and their roles.

Instructions

List the characters of a manga (by mal_id) with their roles. Get the mal_id from search_manga.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesMyAnimeList numeric ID.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
charactersYes

Schema Changelog

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

  1. Changed1 schema field changedv0.10.0
    • addedOutput schema / properties / characters / items / properties / favorites
      Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
  2. Changed4 schema fields changedv0.9.0
    • addedOutput schema / properties / characters / items / properties / mal_id / exclusiveMinimum
      Added value: +0
    • addedOutput schema / properties / characters / items / properties / mal_id / maximum
      Added value: +9007199254740991
    • changedOutput schema / properties / characters / items / properties / mal_id / type
      Previous value: -"number"New value: +"integer"
    • addedOutput schema / properties / characters / 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": {
+    "characters": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "mal_id": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          },
+          "role": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          },
+          "voice_actors": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "characters"
+  ],
+  "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 this as a read-only operation. The description adds useful detail about including roles and using mal_id, but it does not disclose deeper behavioral traits such as pagination, return size, or sorting. The description is consistent with the 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 short sentences. The main purpose is front-loaded, and the ID-source instruction is exactly the kind of practical information that earns its place. No wasted words.

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?

For a single-parameter, read-only tool with an output schema, the description is complete. It specifies what the tool returns, what input is needed, and how to find that input. There is no major missing information.

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 100%, and the schema already explains that 'id' is a MyAnimeList numeric ID. The description adds value by clarifying that the ID is the manga's mal_id and pointing the agent to search_manga as the source for obtaining it.

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 clearly states the action ('List the characters of a manga'), the resource ('manga'), and the kind of detail returned ('with their roles'). It does not explicitly compare against the sibling get_anime_characters, but the resource 'manga' differentiates the tool well enough.

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 explicitly tells the agent how to obtain the required ID ('Get the mal_id from search_manga'), which is clear and actionable. It does not explicitly discuss when not to use the tool or alternative tools, so it stops short of a 5.

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