Skip to main content
Glama
Grinv

MAL MCP Server

by Grinv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get manga magazines

get_magazines
Read-only

List or search manga serialization magazines and publishers by name to retrieve MAL IDs and manga counts, then use those IDs in the manga search magazines filter.

Instructions

List or search manga serialization magazines/publishers (e.g. Weekly Shonen Jump) with their MAL IDs and manga counts. Use q to search by name, or look up an ID here for search_manga's magazines filter.

Input Schema

NameRequiredDescriptionDefault
qNoFilter by name.
pageNo1-based page number for pagination (1-20000).
sortNoSort direction. Only takes effect together with `order_by`; ignored on its own.
limitNoMax results per page (1-100).
letterNoRestrict results to entries whose title starts with this single letter.
order_byNoField to order by.

Output Schema

NameRequiredDescriptionDefault
pageYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.11.0
    • changedInput schema / properties / page / description
      Previous value: -"1-based page number for pagination (1-1000)."New value: +"1-based page number for pagination (1-20000)."
    • changedInput schema / properties / page / maximum
      Previous value: -1000New value: +20000
    • addedInput schema / properties / q / maxLength
      Added value: +300
    • addedInput schema / properties / q / minLength
      Added value: +1
    • changedInput schema / properties / sort / description
      Previous value: -"Sort direction."New value: +"Sort direction. Only takes effect together with `order_by`; ignored on its own."
  2. Addedv0.9.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-data scope are covered. The description adds useful behavioral detail by saying results include MAL IDs and manga counts and by explaining the relationship to search_manga's magazines filter.

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 compact sentences front-load the tool's function and then give the key usage instruction. There is no redundant or filler text.

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?

The description is complete for a read-only lookup/list tool: it explains what is returned, how to search, and how the result feeds another tool. Rich schema coverage and an output schema mean pagination and return structure need not be repeated.

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%, so the schema already documents all six parameters, including pagination, sorting, and filtering behavior. The description only elaborates on `q`, but with full schema coverage that is sufficient to meet the baseline.

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 states a specific verb and resource: list or search manga serialization magazines/publishers. It also names a concrete example, clarifies that results include MAL IDs and manga counts, and connects the tool to search_manga's magazines filter, so an agent can distinguish it from siblings.

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 gives clear usage context: use `q` to search by name, or look up an ID for use with search_manga's `magazines` filter. It does not explicitly state when not to use this tool, but the intended usage is clear and tied to a related sibling workflow.

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

Deploy Server

Other Tools