Skip to main content
Glama
Sign In
MyAnimeList MCP Server

MyAnimeList MCP Server

by MorpKnight
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_anime

Search MyAnimeList for anime by title or keyword, with pagination and result count control to find specific entries.

Instructions

Search MyAnimeList anime by title or another text query.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "get_anime"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
limitNoNumber of results
offsetNoPagination offset

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It merely states 'Search MyAnimeList anime' without addressing read-only nature, pagination behavior, rate limits, or handling of no results. The schema reveals limit/offset, but the description does not explain these behaviors.

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?

The description is a single concise sentence, front-loaded with the action and resource. Every word adds value with no redundancy or filler, making it highly efficient.

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

Completeness3/5

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

Given the simple nature of the tool and complete parameter schema, the description is minimally sufficient for basic use. However, without an output schema or annotations, it does not clarify what the search returns (e.g., list format, pagination details) or how it fits with sibling tools, leaving some gaps in context.

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 q ('Search query'), limit ('Number of results'), and offset ('Pagination offset') are all documented. The description's 'by title or another text query' adds only a minor clarification for q and does not provide additional semantics beyond the schema, hence a baseline 3.

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 uses a specific verb 'search' and clearly identifies the resource 'MyAnimeList anime' as the target. This distinguishes it from sibling tools like get_anime_details (which retrieves specific details) and get_anime_ranking (which retrieves rankings), making the purpose unambiguous.

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?

The description implies the tool is to be used when the agent has a title or text query to search for anime. However, it provides no direct guidance on when not to use it or when to prefer sibling tools like get_anime_details or get_anime_list.

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