Skip to main content
Glama
Grinv

MAL MCP Server

Get a random anime

get_random_anime
Read-only

Discover new anime by retrieving a random anime with full details. Filter by safe-for-work content or exclude ecchi genres.

Instructions

Return one random anime (full details). Good for discovery / suggestions. No official-API fallback exists for this tool — it always needs Tenrai itself to be reachable.

Input Schema

TableJSON 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.
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

TableJSON Schema
NameRequiredDescriptionDefault
urlNo
rankNo
typeNo
yearNo
airedNo
scoreNo
titleNo
airingNo
genresNo
mal_idYes
ratingNo
seasonNo
sourceNo
statusNo
themesNo
membersNo
studiosNo
trailerNo
durationNo
episodesNo
externalNo
moreinfoNo
synopsisNo
broadcastNo
favoritesNo
image_urlNo
licensorsNo
producersNo
relationsNo
scored_byNo
streamingNo
backgroundNo
popularityNo
demographicsNo
ending_themesNo
title_englishNo
opening_themesNo
title_japaneseNo
title_synonymsNo
explicit_genresNo
Behavior5/5

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

Annotations already provide readOnlyHint and openWorldHint, indicating safe, non-deterministic behavior. The description adds that no official-API fallback exists and it always needs Tenrai reachable, which are valuable behavioral traits beyond annotations. No contradiction.

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, front-loaded with core purpose, no wasted words. Efficiently conveys the essential information.

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?

With an output schema present, return values are covered. Description covers purpose, usage hint, and a fallback limitation. Could explicitly mention randomness or lack of filtering beyond parameters, but overall sufficient for a simple random tool.

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%, with detailed descriptions for both sfw and sfw_strict parameters. The tool description adds no additional parameter meaning beyond 'full details' about output, 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?

The description clearly states 'Return one random anime (full details)' with a specific verb and resource, and positions it for discovery/suggestions. It differentiates from siblings by specifying 'anime' in a family of random tools.

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 indicates use for discovery/suggestions, providing clear context. However, it lacks explicit when-not or alternative comparisons to siblings like get_anime or get_random_manga, though the purpose is implicitly differentiated.

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