MAL MCP Server

Overview Schema Source Related Servers Discussions Admin

Get a random person

get_random_person

Read-only

Pick a random MyAnimeList person—voice actor, director, or author—for discovery and trivia; use the returned mal_id with get_person for anime, manga, and voice-role details.

Instructions

Return one random person — voice actor, director, author (core details: no anime/manga/voice_roles — call get_person with the returned mal_id for those). Good for discovery / trivia. No official-API fallback exists for this tool — it always needs Tenrai itself to be reachable.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`url`	No
`name`	No
`about`	No
`anime`	No
`manga`	No
`mal_id`	Yes
`birthday`	No
`favorites`	No
`image_url`	No
`given_name`	No
`family_name`	No
`voice_roles`	No
`alternate_names`	No
`credits_truncated`	No
`total_anime_credits`	No
`total_manga_credits`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.10.0Aug 24, 2026

addedOutput schema / properties / credits_truncated

Added value: +{
+  "const": true,
+  "type": "boolean"
+}

addedOutput schema / properties / total_anime_credits

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / total_manga_credits

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

Changed15 schema fields changedv0.9.0Jul 30, 2026
- addedOutput schema / properties / anime / items / properties / mal_id / exclusiveMinimum
```
Added value: +0
```
- addedOutput schema / properties / anime / items / properties / mal_id / maximum
```
Added value: +9007199254740991
```
- changedOutput schema / properties / anime / items / properties / mal_id / type
```
Previous value: -"number"New value: +"integer"
```
- addedOutput schema / properties / anime / items / required
```
Added value: +[
+  "mal_id"
+]
```
- addedOutput schema / properties / favorites / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / favorites / minimum
```
Added value: +0
```
- changedOutput schema / properties / favorites / type
```
Previous value: -"number"New value: +"integer"
```
- addedOutput schema / properties / mal_id / exclusiveMinimum
```
Added value: +0
```
- addedOutput schema / properties / mal_id / maximum
```
Added value: +9007199254740991
```
- changedOutput schema / properties / mal_id / type
```
Previous value: -"number"New value: +"integer"
```
- addedOutput schema / properties / manga / items / properties / mal_id / exclusiveMinimum
```
Added value: +0
```
- addedOutput schema / properties / manga / items / properties / mal_id / maximum
```
Added value: +9007199254740991
```
- changedOutput schema / properties / manga / items / properties / mal_id / type
```
Previous value: -"number"New value: +"integer"
```
- addedOutput schema / properties / manga / items / required
```
Added value: +[
+  "mal_id"
+]
```
- addedOutput schema / required
```
Added value: +[
+  "mal_id"
+]
```
Addedv0.8.0Jul 29, 2026
Removedv0.7.1Jul 22, 2026
Addedv0.2.0Jun 29, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it discloses that the returned record omits anime/manga/voice_roles and that no official-API fallback exists, so Tenrai must be reachable. Those are meaningful operational constraints that annotations do not carry.

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 tight sentences: purpose and scope first, usage second, availability caveat last. Parenthetical detail is dense but purposeful, and there is no filler.

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 no-parameter random lookup with an output schema and read-only/open-world annotations, the description supplies the needed purpose, scope limits, alternative route, and availability caveat. Nothing essential is missing.

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?

This is a zero-parameter tool, so there is nothing for the description to disambiguate and the baseline is 4. The description correctly avoids inventing input semantics and uses its space for output scope and alternatives.

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 (return one random person) and enumerates the person types it covers. It explicitly differentiates from get_person by naming the fields it omits and the follow-up call to use for them.

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?

Gives an explicit use case ('Good for discovery / trivia') and an explicit alternative condition: if anime/manga/voice_roles are needed, call get_person with the returned mal_id. That is clear when-to-use and when-to-switch guidance.

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

Deploy Server