MAL MCP Server

Overview Schema Source Related Servers Discussions Admin

Get a random person

get_random_person

Read-only

Discover random anime industry professionals—voice actors, directors, or authors—with complete profile details, staff credits, and voice roles. Use for trivia, exploration, or finding a new person of interest.

Instructions

Return one random person — voice actor, director, author (full details, shaped exactly like get_person: staff credits capped at 200, voice_roles at 50). Good for discovery / trivia. No official-API fallback exists for this tool — it always needs Tenrai itself to be reachable.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON 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.5/5.0

Behavior4/5

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

Annotations already establish read-only and open-world behavior, so the bar for extra disclosure is lower. The description adds meaningful behavior beyond annotations: staff credits capped at 200, `voice_roles` capped at 50, and no official-API fallback with a hard dependency on Tenrai reachability. Nothing contradicts 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?

The description is compact and front-loaded, with every sentence earning its place. It covers purpose, entity scope, output shape, use case, and operational constraints without redundancy.

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 zero-parameter tool with an output schema and readOnly/openWorld annotations, the description provides complete operational context: what is returned, how it is shaped, when to use it, and what infrastructure is required.

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 has no parameters and schema coverage is 100%, so there is no parameter burden for the description to carry. The baseline for a zero-parameter tool applies.

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?

The description opens with a specific verb and resource: 'Return one random person', then disambiguates the entity type by listing 'voice actor, director, author'. It further ties output shape to 'get_person', making its relationship to sibling tools clear.

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?

It explicitly states a clear use context: 'Good for discovery / trivia'. It does not name alternatives or exclusion conditions, but the context is sufficient for an agent to select this tool appropriately.

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

Deploy Server