Skip to main content
Glama

jikan_top_anime

Read-onlyIdempotent

Fetch ranked anime titles from MyAnimeList with optional filters for page, type, limit, and ranking category, such as airing, upcoming, popularity, or favorites.

Instructions

Get top-ranked anime from MyAnimeList.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jikan_top_anime"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
typeNotv, movie, ova, special, ona, music
limitNo
filterNoairing, upcoming, bypopularity, favorite

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds no behavioral context beyond that: it says nothing about page size, result caps, ordering stability, or rate limits on the MyAnimeList source, so it is only minimally additive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. It is efficient, though the brevity is partly the cause of the missing guidance rather than a virtue in itself.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Four optional parameters, 50% schema coverage, and no output schema, yet the description says nothing about pagination behavior, the 25-per-page cap typical of this source, or what fields a ranked entry returns. For a list endpoint the agent cannot call it well without guessing at limit/page semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: 'type' and 'filter' carry inline enums, but 'page' and 'limit' are bare numbers. The description supplies no meaning for either — no page size, no maximum, no default — so it fails to compensate for the undocumented half of the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Get top-ranked anime') and the source (MyAnimeList), and the 'top-ranked' qualifier distinguishes it from jikan_search_anime and jikan_get_anime. It does not explicitly name those siblings, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus jikan_search_anime (query-based) or jikan_get_anime (single record by ID). The agent must infer the ranking-list use case purely from the word 'top-ranked'.

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