Skip to main content
Glama
Grinv

MAL MCP Server

Get a random manga

get_random_manga
Read-only

Discover new manga to read with a random pick from the full library. Get complete details for each suggestion.

Instructions

Return one random manga (full details). Good for discovery / suggestions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNo
rankNo
typeNo
scoreNo
titleNo
genresNo
mal_idYes
statusNo
themesNo
authorsNo
membersNo
volumesNo
chaptersNo
synopsisNo
favoritesNo
image_urlNo
publishedNo
relationsNo
scored_byNo
backgroundNo
popularityNo
publishingNo
demographicsNo
title_englishNo
serializationsNo
title_japaneseNo
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, covering safety and randomness. Description adds that it returns full details, which is consistent. No contradictions; behavioral traits are adequately disclosed.

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?

Extremely concise: two sentences, front-loaded with function, no wasted words. Every sentence earns its place.

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?

Tool has no parameters and annotations cover key traits. Output schema exists, so description doesn't need to detail return values. 'Full details' is vague but acceptable given the schema.

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?

No parameters, so schema coverage is 100%. Description does not need to add param info; baseline of 4 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?

Clearly states the tool returns one random manga with full details, distinguishing it from sibling tools like get_manga (specific) and search_manga (search). The phrase 'Good for discovery / suggestions' further clarifies its use.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implicitly indicates use for discovery/suggestions but lacks explicit when-not-to-use or alternatives. Among siblings with random tools (e.g., get_random_anime, get_random_character), no guidance on which to choose.

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