Skip to main content
Glama
Sign In
MyAnimeList MCP Server

MyAnimeList MCP Server

by MorpKnight
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_manga

Search MyAnimeList manga by title or keyword to find and paginate through matching titles.

Instructions

Search MyAnimeList manga 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_manga"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
limitNoNumber of results
offsetNoPagination offset

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It only states the search function and offers no details on pagination, result ordering, or output structure. There is no mention of side effects or limitations, leaving significant room for misjudgment.

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, front-loaded sentence with no fluff. It efficiently communicates the core purpose, matching the standard of high-conciseness examples.

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?

The tool is simple, but with no output schema and sparse annotations, the description should explain what the search returns. It does not mention result format or list properties, leaving the agent under-informed about the tool's output.

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%, so baseline is 3. The description adds minimal nuance by clarifying 'q' is a title or text query, but this is a minor enhancement over the schema's 'Search query'. It does not elaborate on limit or offset behavior.

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?

The description uses a specific verb ('Search') and resource ('MyAnimeList manga'), clearly indicating this is a search tool. It distinguishes from siblings like get_manga_details or get_manga_ranking, but doesn't explicitly contrast with get_manga_list, so it falls 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?

No guidance is provided on when to use this tool versus alternatives. It does not mention exclusions or when get_manga_list or get_anime would be more appropriate, leaving the agent without contextual decision support.

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