Skip to main content
Glama
Grinv

MAL MCP Server

Get broadcast schedule

get_anime_schedule
Read-only

Retrieve anime broadcast schedule filtered by weekday, with options to exclude adult or kids content and paginate results.

Instructions

Get the anime broadcast schedule (air times in JST), optionally for a single weekday (or the unknown/other buckets Tenrai uses for shows with no fixed weekly slot). broadcast is only present for currently-airing shows. Defaults to 25 results if limit is omitted; use page for further results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayNoWeekday to filter by, or `unknown`/`other` for shows with no fixed weekly slot. Omit for the whole week.
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.
kidsNoIf true, exclude entries tagged as children's/kids content. Defaults to false.
pageNo1-based page number for pagination (1-1000).
limitNoMax results per page (1-50).
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.
unapprovedNoIf true, also include entries not yet approved by MAL's moderators (excluded by default). Defaults to false.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYes
resultsYes
Behavior4/5

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

Annotations already indicate read-only and open-world behavior. The description adds valuable context: broadcasts only appear for currently-airing shows, defaults, timezone (JST), and pagination details, going beyond what annotations provide.

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 with no fluff. The main action ('Get the anime broadcast schedule') is front-loaded, and all critical details (timezone, optional day filter, defaults) are included efficiently.

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?

With an output schema present and all behavioral traits disclosed (timezone, conditional fields, pagination), the description is fully sufficient for an agent to understand and correctly invoke the tool without gaps.

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 coverage is 100% with each parameter described. The tool description only adds a note about 'broadcast' being present for currently-airing shows (an output detail), so no extra parameter semantics are provided. Baseline 3 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 clearly states the tool retrieves the anime broadcast schedule in JST, with optional weekday filtering, distinguishing it from search/detail tools. It also mentions special buckets 'unknown' and 'other' for shows without fixed slots, adding specificity.

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 explains optional filtering by weekday and default pagination behavior. While it doesn't explicitly state when not to use it or compare to alternatives, the context of sibling tools makes its purpose distinct enough for proper selection.

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